transforming the 5-branch-types !git model to the 2-branch !hg model with the same functionality

[Arne Babenhauserheide]

Am Samstag, 26. Januar 2013, 14:43:21 schrieb Victor Suba:
> This is a bit misleading.  There is little Git specific or Hg specific in
> either model.

The names come mostly from the origin of the model (git users or hg users).

But there is hg specific stuff in the 2-branch model: Some of its simplification require the more expressive named-branches of hg. For example 
the simple search for the latest tag on a given branch renders it useless to use master only for tags - and Mercurials in-history tags provide the security you get in git by always merging before you tag (making sure that the tag cannot easily be moved without leaving a trace).

On the other hand the 5-branch model has disadvantages in hg, because with its many branches, named-branches clog the namespace (you can’t reuse them easily) and bookmarks have slightly different semantics than git branches (updating to tip gives you the latest changeset regardless of the bookmark). 

So yes, you could use the 5-branch model with hg and an adaption of the 2-branch model in git, but they would not use all the strengths of the chosen versiontracking system.

Best wishes,
Arne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20130127/5ff963ed/attachment.asc>