[PATCH 0 of 2] document convert-repo interfaces

[Giorgos Keramidas]

On 2007-05-20 16:01, Edouard Gomez <ed.gomez at free.fr> wrote:
>On Sun, 20 May 2007 05:59:48 +0300, Giorgos Keramidas wrote:
>> Another point which is important is that some projects with
>> long-lived branches, and a clear plan of supporting backwards
>> compatibility for their existing userbase may need the reverse
>> too, i.e.:
>> 
>>    Once they switch to Hg, a 'gateway' between Hg commits and their
>>    old CVS tree, which will be maintained for historical reasons.
>>    Users who depend on the existing CVS-based infrastructure, can
>>    continue to work with the tools they find comfortable, but the
>>    cutting edge of development has moved to Hg and happens there
>>    first.
> 
> Two way sync is a bit complicated but still feasible, see the bzr svn 
> branches.

Ah, what I wrote came out entirely wrong. I didn't mean two-way sync,
but more like something following the plan:

    * Name a 'flag day', and freeze CVS for a short while.

    * Import the latest CVS code into Mercurial (i.e. using something
      like cvs20hg which can pull incrementally only the changes since
      the last run)

    * Switch to Hg as the main repository

    * Set up a 'gate' which pushes Hg changes to CVS too.

    * Treat CVS as a read-only repository for all humans, except for the
      'gate' commits which keep it up to date with Hg changes

>> The usage is also not so well documented.  I was literally scared away
>> the first time I looked at convert-repo because of the lack of 'Average
>> Joe User' documentation.  We don't need something too fancy, mind you.
>> Just a manpage with usage examples would make things go a long way :)
> 
> One of my patches dump an help message at least :-)
> 
> But i'll put a manpage on my todo list.
> 
> I've put on my site an updated queue, have a look at it and don't 
> hesitate giving feedback.
> http://ed.gomez.free.fr/mercurial/convert-repo-queue.tar.bz2

I will, thanks :)