[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion use for Kernel work

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-02-27 17:53:52 CET

On Thu, 2003-02-27 at 11:34, Zack Brown wrote:
> The fact is, BitKeeper didn't just drop into the kernel development
> process. It came only after a long period of communication between
> kernel developers (mainly Linus) and Larry, to get the base set of
> features exactly right.

And, frankly, I wouldn't want to see Subversion do the same thing, if it
means adding more ways to do the same thing, or commands tailored for
particular projects. One of the plusses we have over Bitkeeper (in my
mind) is a smaller command set.

> 1) speed
> 2) cross-repository merging

Of course, these things are always nice. (An alternative to
cross-repository merging, which is a bunch of client code, is
cross-repository partial synchronization, which is a bunch of server
code. Both will let you do distributed development; the first is more
convenient when you want to merge from lots of different sources without
setting up copies first; the second requires more storage but allows you
to work better offline.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 27 17:54:47 2003

This is an archived mail posted to the Subversion Dev mailing list.