Using bookmarks in Mercurial itself
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Fri Jun 17 17:30:09 CDT 2011
On Fri, Jun 17, 2011 at 11:34:45PM +0200, Arne Babenhauserheide wrote:
> On Friday 17 June 2011 14:17:22 Pierre-Yves David wrote:
> I still think that liquid history is a nice idea, but it is a different
> usecase: You try to get the history nice by hiding how you got there instead
> of making it easier to read but keeping the way you took.
>
> From a copyright perspective going the second route might even be imperative:
> Only with that can you track who exactly added which change.
Nothing should prevent you to keep intermediate version of rewritten changeset.
Again, the issue with (grouped) branch + merge is that it prevent you to[1]:
* Summit multiple clean changeset that finally lead to an higher level feature (macro-change)
* Reorder "macro-change"
* Split "macro-change" in multiple "macro-change"
This lead to poorer history.
--
Pierre-Yves David
[1] Or make it very complicated to
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
More information about the Mercurial-devel
mailing list