On Tue, 2 Sep 2003, Keith Whitwell wrote:
>
> It sounds like it should be sophisticated enough to allow a transition where
> sourceforge cvs continues to work and be updated, and accept updates of its
> own.
I'm afraid that it isn't quite _that_ seamless.
The BK -> CVS/SVN gateway is one-way only: you can import a CVS tree (with
full history) into bitkeeper, but after that the current tools only
support a read-only CVS repository.
So committers would have to jump in to the BK model. In Linux, this was
pretty painless, since people were used to just sending me patches, and I
was the only "committer" for the standard tree (and I wrote a number of
tools to make it easy to use BK with an email patch interface - some of
the central parts of which are now in the standard BK release).
> That is it *sounds* like we could have some developers using cvs, some
> bitkeeper but have changes to some notional "trunk" propogate to and be
> visible in both systems - if done rapidly enough there should be few conflicts
> requiring manual resolution.
You could in theory try to do some kind of two-way gateway, exporting any
CVS commits as patches and applying them to the BK tree (and then trying
to re-merge the CVS tree, ugh), but it would get really nasty really
quickly if there was any kind of merge issues.
So I would suggest against it. If there are enough people in the core
group that are interested in BK, and have some familiarity with it, some
of them might be willing to just act as "patch monkeys" and apply patches
from email into the BK tree from other developers that don't use BK (ie
the non-BK developers would technically lose direct write capability, but
by virtue of being trused they'd get their patches applied asap anyway).
I don't think there are that many really active DRI people, so I suspect
it should be manageable.
But no, it's not going to be totally painless.
Linus
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
