Does hgsvn support lossless, bidirectional svn<->hg sync (was:[PATCH] Some yasvn2hg patch)

Kunle Odutola Kunle_Odutola at hotmail.com
Wed May 9 12:53:29 CDT 2007


Hi,

> > > For the record, hgsvn is not meant as a one-way converter, but a
> > > tool to use Mercurial with SVN checkouts.
> >
> > Can you explain further what you mean by this statement please?
> >
> > Does hgsvn essentially allow a user to pull Subversion project(s) into
> > Mercurial repository(s), work on the repository(s) in Mercurial as usual
> > then, push the changes incrementally - including all hg commit history -
> > back to the original Subversion project(s)?
>
> For now it only handles the "pull" part. (which is already useful if you
> don't have commit access to the SVN repo :-))
>
> I have ideas and a start of implementation for the "push" part.
> However I fear the "push" will not be as lossless as the "pull" is,
> because the high-level SVN API doesn't allow, to my knowledge,
> specifying the commit date or author.

Thanks for the info. It's a shame that the high-level SVN API prevents the
sync from being truly lossless.

How much work would you estimate would be involved in adapting hgsvn to
produce an equivalent tool - say hg_sync_p4 - that syncs with Perforce
depots rather than Subversion (with both "pull" and "push" implemented)?

Kunle



More information about the Mercurial mailing list