[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Xen repository

On Mon, 2005-05-23 at 10:11 +0100, Ian Pratt wrote:
>  > > cogito (the renamed git) looks pretty 'raw' at the moment. I did of 
> > > playing around with mercurial last night and was impressed with how 
> > > much functionality it has in just 2k lines of python.
> > > 
> > > One option is to just have a public CVS repo, and then everyone can 
> > > use whatever SCM tool they prefer as pretty much everything has an 
> > > 'import from CVS' feature. The only dowsnide to this is CVS's 
> > > inability to represent the current branch structure.
> > >  
> > how about using subversion instead of CVS? 
> If we go down this interim route I think I'd rather have plain CVS as
> the 'lingua franca'. 
One thing I don't particularly like about cvs is that it only tracks
file changes rather than having a notion of a changeset.  There are some
obvious disadvantages with this such as with changes that affect more
than one file (as most do), and ordering and such, but I have another.
When I find a regression without an obvious cause, it's often helpful to
do a binary search through the changesets between the current and
last-known working version to efficiently find out where it broke.  This
has been valuable for finding the source of both bugs and perf
regressions in the kernel before.  This is really hard to do with cvs.

I've looked at cogito some and like it, I know it will let us do this.
I don't know about mercurial, I haven't looked at it other than the
couple of emails I had seen out on lkml announcing it.  I didn't think
anyone was using it.

Paul Larson

Attachment: signature.asc
Description: This is a digitally signed message part

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.