Jay -- this synthesis is so twistedly ingenious, I'm wondering
if you can make SVN get into BitKeeper! After all, that's just
plain old SCCS. I was ready to shed a nostalgic tear when I
needed a new ntpd, which switched to BitKeeper, and got that,
and checked it out, and saw -- oh my G-d -- SCCS subdirs and
s.prefixes! And with your recompiling skills with C# (gasp),
should be easy to reverse-engineer whatever they added. :-)
(I'm also curious what saurik means?)
At this point, I'm going to try to keep a project of mine in
_all three_ VCS's simultaneously. You need to keep .cvsignore,
svn:ignore and whatever BitKeeper has so that they don't step
on each other's toes; have the $Rev$, $Id$, and that twisted
pretzel-like SCCS keyword everywhere in sync; and what not else,
but that would be very interesting!
I was surprised that not much info is available about the
BitKeeper. Below's an old e-mail outlining their plans, and
easy graphical merge seems to be what they wanted as their
killing feature all along. I hope SVN's merge is comparable.
We need to get some seriously intertwined project trees to
compare -- perhaps get the Linux kernel tree and mimic its
history in SVN?
Network replication (vs. file backup) of the whole repository
is the best backup. In BitKeeper, you can replicate the repository
easily, with bk clone. CVS has CVSup, and with SVN, I guess
svn cp is equivalent? In that case, we're right there already...
So here's the link I found, and I wonder what other people
think about SVN vs. BitKeeper in terms of the future SVN ideas!
http://mail.python.org/pipermail-21/mailman-developers/1999-October/006014.html
Cheers,
Alexy Khrabrov :: www.setup.org :: svn => badlog.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 3 19:55:28 2002