From: Anthony PERARD <anthony.perard@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: Sunseting mercurial
Date: Mon, 26 Mar 2018 11:56:49 +0100 [thread overview]
Message-ID: <20180326105649.GA2208@perard> (raw)
In-Reply-To: <5AB8E91C02000078001B6023@prv1-mh.provo.novell.com>
On Mon, Mar 26, 2018 at 04:35:40AM -0600, Jan Beulich wrote:
> >>> On 25.03.18 at 04:46, <cardoe@cardoe.com> 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
Cardoe, if you mean "often out of date", that's true, but only by 10min
(which is the frequency at which a cron run).
> > of this email its several weeks out of date.
I'm guessing it's out of date just because I didn't thought of checking
if it was working after the recent server update. I only check every 2
months. I'm going to fix the script now.
> > 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).
>
> Speaking of mercurial, Anthony, wasn't it you who looks after the
> git -> hg mirroring? The unstable.hg branch didn't get updated
> after the last push from staging to master. Could you please see
> if this can be rectified (assuming that my memory didn't fail me in
> the first place, and it was someone else)?
Yes, that me that looks after it. I'll fix the mirror.
Thanks,
--
Anthony PERARD
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-26 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 2:46 Sunseting mercurial Doug Goldstein
2018-03-26 10:35 ` Jan Beulich
2018-03-26 10:55 ` Roger Pau Monné
2018-03-26 10:56 ` Anthony PERARD [this message]
2018-03-26 13:18 ` Anthony PERARD
2018-03-26 13:44 ` Jan Beulich
2018-03-26 13:56 ` Doug Goldstein
2018-03-28 11:25 ` George Dunlap
2018-03-28 11:54 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180326105649.GA2208@perard \
--to=anthony.perard@citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.