Re: [Monotone-devel] cvs_import

[Hendrik Boom]

On Wed, Jul 17, 2013 at 08:47:54PM +0200, Markus Wanner wrote:
> Hendrik,
> 
> On 07/15/2013 07:21 PM, Hendrik Boom wrote:
> > Just wondering what the current status of of monotone's CVS support;
> > in particular, cvs_import, csv_pull. cvs_sync, cvs_takeover, and I've 
> > heard there's even a cvs_push.
> 
> Standard monotone's cvs_import works fine for simple cases. I didn't do
> any work on the cvs_import branch and I don't think it's in a usable state.

So standard monotone's cvs_import is different from what's on the 
cvs_iport branch, as described on http://wiki.monotone.ca/CvsImport/, 
even assuming that page is up to date.

And there's also 
http://wiki.monotone.ca/Branches/nvm.cvsimport-branch-reconstruction/

which bears your name and says "Status: Work in Progress Still 
close to completion".  Do you know if that status is still valid?  or 
if anyone else might have worked on it or be on the case?

Is it still worth doing?

> 
> You might want to check if cvs2svn can be of help. They have a nice git
> export function and their CVS sanitizer code is field proven. I'm not
> sure if you can get that into monotone, though.
> 
> > Is the conversion a one-time event, or can it keep up with further 
> > revisions on the cvs site withoug having to start over?
> 
> There are all one-time conversion options, which need access to the RCS
> files on the CVS server.
> 
> tailor may be an option, if you want a continuous mirror.

THe main need for a continuous mirror I see would be during transition 
from CVS to monotone. There would likely be work in progress on the 
old system while the new one is being adopted.

> It certainly
> has a monotone plugin. I'm not sure what the status of cvs_sync is, but
> it's intended to provide continuous synchronization as well.

tailor (http://darcs.net/RelatedSoftware/Tailor)looks interesting, 
thanks.

-- hendrik

> 
> Regards
> 
> Markus Wanner