This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] bitkeeper gone in 2 weeks - which RCS?

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] bitkeeper gone in 2 weeks - which RCS?
From: Matt Mackall <mpm@xxxxxxxxxxx>
Date: Wed, 15 Jun 2005 18:16:48 -0700
Cc: Andrew Thompson <andrewkt@xxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Mercurial List <mercurial@xxxxxxxxxxx>
Delivery-date: Thu, 16 Jun 2005 07:58:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282265@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282265@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Jun 15, 2005 at 11:11:44PM +0100, Ian Pratt wrote:
> > > Because of the way we use renames when doing linux version 
> > > upgrades it would be really useful to get this added.
> > 
> > Matt Mackall wrote:
> > Well someone can relay to them that rename support should 
> > happen very soon. 
> That's great to hear. One of the reasons we're keen on mercurial is that
> the rate of progress is so impressive. 

hg copy is now in tip, but there's not much there yet except recording
that a copy/rename happened.
> > I'm still not convinced of the value of 
> > per-file checkins (if you need per-file checkins, your 
> > commits are too big) but I'm not completely immune to reason.
> We're intending to incrementally import our BK repo a changeset at a
> time, retaining as much of the meta data as possible. Since we have
> per-file info it seems a shame to throw it away. We may end up just
> creating a summary of it in the changeset comment.

It's unlikely that we'll get the UI bits for file comments done in the
next two weeks, but putting everything in the summary as:


..should preserve things well enough.

Mathematics is the supreme nostalgia of our time.

Xen-devel mailing list