[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: RFC/preview: automate interface for cvssync
From: |
Christof Petig |
Subject: |
Re: [Monotone-devel] Re: RFC/preview: automate interface for cvssync |
Date: |
Wed, 26 Jul 2006 15:10:08 +0200 |
User-agent: |
Thunderbird 1.5.0.2 (X11/20060521) |
Koen Kooi schrieb:
> Could this be used to setup up a read-only SVN/CVS mirror for an
> existing monotone project?
yes and no ...
you can not map monotone's meshed ancestry onto a linear path. So you
can only export a linear subgraph of each branch. Multiple heads within
one branch are only common in a distributed VCS (which neither SVN nor
CVS is).
We do mirror our monotone projects onto a remote CVS server using
revision 1f4899bea28adfd740ebf1bf7b7e92425056b436, but currently you
have to start with the CVS tree to use it. [A _possible_ rosterified
revision is e025e7e5a4826f8a3f117ece343ee99c6306f9c2, I broke the
cvssync branch with an unwanted back-propagate from the rewrite branch
afterwards]
The rewrite is 70% finished and should offer the following benefits:
- faster (of course)
- Use a robust ancestry approach instead of time comparisons for
mtn->CVS. Has failed too many times.
- migration path for old sync information
- Allow to start from a monotone repository and push into an empty CVS
repository.
lateron:
- minimal SVN remote import functionality (you might be able to hack
export functionality in a few hours once this is finished).
- minimal git remote import functionality
Christof
signature.asc
Description: OpenPGP digital signature