Re: [Monotone-devel] Current status of cvssync?

[Christof Petig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

address@hidden schrieb:
> On Fri, Mar 27, 2009 at 08:30:51AM -0400, address@hidden
> wrote:
>> On Fri, Mar 27, 2009 at 10:01:47AM +0100, Markus Wanner wrote:
>>> Hi,
>>> 
>>> address@hidden wrote:
>>>> Can anyone enlighten me? (a) Is it usable? (b) is it usable for
>>>> those that aren't developing monotone? (c) does it have serious
>>>> bugs or deep concptual problems?
>>> AFAICT Christof has used it for his own work, so I guess
>>> something between (a) and (b), but maybe also (c), otherwise it
>>> would have landed on mainline  ;-)
> 
> Among the three branches I found, namely,
> 
> net.venge.monotone.cvssync, 829 days old 
> net.venge.monotone.cvssync.attrs, 681 days old, and 
> net.venge.monotone.cvssync.refactor, 48 days old,
> 
> which is the one most likeky to work?

As long as it compiles (I remember some loose ends at my side when I did
the last propagate) refactor is the best guess.

I have some open issues:
- - there seems to be an issue with merges in some of my tree
synchronizations (longstanding problem)
- - $Id$ expansions are not handled as well as they should - I have ideas
to fix this but lacked development time.

But AFAIK all tests pass - and you can combine the mtn_cvs binary from
the cvssync.refactor branch with the newest mtn binary - mtn_cvs is just
a wrapper to sync mtn with cvs (via mtn automate stdio and remote cvs
protocol).

Feel free to do some tests - I can not promise to fix issues - but I am
willing to do so (especially you provide test cases).

> Or is the 48-day one the best because it's still being maintained 
> somewhat and using it would help identify problems?
> 
> Is there any documentation for cvssync?

I remember extending monotone.texi for documentation, but it no longer
contains mtn_cvs changes? Actually mtn_cvs --help should give you a good
first idea.

> Is there any relation between cvssync and the mtn cvs pull that's 
> documented in the mainline version?

... Maybe this _is_ the documentation for cvssync ;-)

The effort for merging to mainline just exceeded the time a was able to
spent on this branch during the past years - mtn_cvs shares a lot of
common infrastructure with mtn (sanity, argument passing) so it is not
an easily separated project.

    Christof
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknnhxEACgkQng+R+0ucfO30IQCfRx0Y46iXa/5U/QC/2gD/8EPY
EpEAoMzBsJ1sK4A1URlDUQsA4mzI9N6z
=R3Cv
-----END PGP SIGNATURE-----