Re: [Xen-devel] Sunseting mercurial

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 28.03.18 at 13:25, <dunlapg@xxxxxxxxx> wrote:
> On Mon, Mar 26, 2018 at 2:56 PM, Doug Goldstein <cardoe@xxxxxxxxxx> wrote:
>> On 3/26/18 5:35 AM, Jan Beulich wrote:
>>>>>> On 25.03.18 at 04:46, <cardoe@xxxxxxxxxx> wrote:
>>>> Its been officially 5+ years since Xen has moved to git so I propose we
>>>> start thinking about when to retire the mercurial mirrors. At this point
>>>> the last stable version to be tracked in mercurial is 4.4 which is long
>>>> out of any form of support. I know some vendors still have support for
>>>> versions of Xen down to 4.1 but let's be realistic, there's not a flurry
>>>> of development happening in those old versions. The mercurial mirror is
>>>> often out of date (I know someone that's tried to use it) and in fact as
>>>> of this email its several weeks out of date.
>>>>
>>>> So maybe its time we start thinking about sunsetting the mercurial
>>>> mirrors and use those resources for more practical uses.
>>>
>>> This was brought up before, and I continue to agree _as long_ as
>>> our web representation of the tree gains something similar to
>>> hg's "annotate" functionality. Without that I find it quite hard to
>>> locate commits most recently changing a line or an area of code.
>>> Of course aiui this can be done from the command line, but only if
>>> one happens to have a repo on the particular machine (which for
>>> example I don't have or intend to have at home).
>>>
>>
>> While I agree that gitweb should be changed to support showing that,
>> there exist a few options out there as well that work today.
>>
>> https://gitlab.com/xen-project/xen/blame/staging/xen/common/Makefile 
>> https://github.com/xen-project/xen/blame/staging/xen/common/Makefile 
>>
>> Browse to any file and click the Blame button or remember the URL and go
>> to it manually or here's a 10 second script.
> 
> Jan, would the above two options be functional enough for you?

In the worst case the above would probably work, but Ian has
turned on "blame" for xen.git already, which I much prefer over
using secondary repos.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel