On 04.11.2011 22:32, Andreas Kupries wrote:
Does hg have something git's rebase and other history rewriting operations ?
Yes - hg supports all of them and more (via various bundled [1] and endless count of community extensions), but as you know, history rewriting kills any repo/repo synchronization in any DVCS. Thus, thinking of the partial Fossil/Git bridge, let's focus on ideal case - no rebases, full DAG synchronization.
If not, how do hg and the synchronizer (dulwich?) cope when the git repository they talk to undergoes such a rewrite ?
Dulwich is not a merge-application - dulwich is just a well designed Git API (protocol and container format).
In the case of Mercurial/Git bridge, the actual synchronizer is the hg-git itself (mercurial extension), which was started as common effort with github.com, but these days is actually maintained by hg-subversion team (with Augie Fackler [2] as lead)
[1] http://mercurial.selenic.com/wiki/RebaseExtension [2] https://bitbucket.org/durin42/hg-git/changesets _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
