Re: [Monotone-devel] cvs_import/sync questions

[Christof Petig]

Emile Snyder schrieb:
> Hi all,
>
> Is it worth looking at cvs bugs on the main branch, or is the cvssync
> branch going to supersede it?  Is cvssync close to merging?  Is cvssync
> stable enough that I should try to figure out bugs on it, or is it still
> in flux and I should just let Christof do his thing?

I have some things still in my TODO list for cvs_sync:

- fix the current failure of t_cvspull_separate (should be easy)
- fix the failure of t_cvspull_samedirname (should be easy)

- make sure that I'm ignoring self modifying files (e.g. $Id$) well
enough on commit

- make the history reconstruction algo smarter so it does not
reconstruct the full history but constricts to the last revision (for
now, branches might cause more complex setups). This should speed up
cvs_* on deep projects (without --since) by some orders of magnitude.
[This would fix the first bug as well]

- make cvs_push collect some intermediate changelogs when it commits a
merge point ("merge of X and Y" is not too informative if you don't have
the monotone database)

#### far future ######

- make cvs_push work with two children (select which path to take)
- side branch support
- cvs push into an empty repository?
- import of a CVS working directory (so you don't have to contact the
CVS server if you want to commit via monotone)

Of course any help is appreciated (please coordinate! ;-) ). Perhaps a
working "tailor" module (inter VCS syncing scripts) is the way to go (it
already has darcs, svn, cvs, ~monotone~). I did not evaluate it (any
reports welcome) or compared it to my cvs_push/pull.

   Christof

signature.asc
Description: OpenPGP digital signature