Re: [Xen-devel] Sunseting mercurial

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Mon, Mar 26, 2018 at 04:35:40AM -0600, 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).

AFAICT this could be enabled by setting:

$feature{'blame'}{'default'} = [1];

In the gitweb configuration file [0][1].

Roger.

[0] https://git-scm.com/docs/gitweb#gitweb-arguments
[1] https://git-scm.com/docs/gitweb#gitweb-blame

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