-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Saturday, January 24, 2004, at 09:15 PM, Jon Portnoy wrote:


On Sat, Jan 24, 2004 at 07:11:26PM -0800, Robin H. Johnson wrote:
What about BK?
BK works much better than CVS/Subversion for kernels, and don't see any
major reasons not to use it.



The major reason not to use it is that it would rip apart the project.


A significant number of devs and users would be fairly likely to depart
if we were relying on bitkeeper. The license terms are _highly_
authoritarian and controversial. I refuse to deal with the mess (and
nasty PR) it would leave, personally.

For instance, if you work for a company that sells products that compete
with bitmover ... you must purchase a bk license which is several thousand
USD.


It doesn't matter if you don't personally work on it, it doesn't matter if you
in your own time work on open source software. Heck if you work on CVS
you can't use bk without buying a license.


bk is nice in some respects, but personally I think cvs could and should
be actively worked on to add function that even subversion and bk
doesn't have.

As an example I think it would be quite handy to have n branches in a cvs
tree but allow for "common" changes to pushed across a set of branches all
at once in a single commit. Or allow for a patch to start in one branch but
then allow a developer to push the patch to other branches but marked
as experimental. So a normal cvs co / update of that branch it was pushed
to would not get the patch BUT a maintainer / developer type could
get a list of these pending 'experimental' patches, selectively apply them
and then "promote" them so they are commited to the branch so a
cvs co -r thatbranch would then have that "promoted" patch, otherwise
to get the experimental pending patches one would have to do something
like cvs co -r thatbranch --experimental.


Call me crazy but I think cvs needs some lovin'.

Tom Gall
gentoo -- God started with stage 1, shouldn't you?
tgall aatt uberh4x0r.org
tom_gall aatt mac.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAE0IeNM6ZoaBWhQkRAgcKAJ9yki/OfbeZKOaw1AfPgZfe20qx5ACeKNWc
Bgda6HL/YN5gjYWmOz2Qb1U=
=R6/f
-----END PGP SIGNATURE-----


-- [EMAIL PROTECTED] mailing list



Reply via email to