How to hide a changeset by committing in another one?

Pierre-Yves David pierre-yves.david at logilab.fr
Mon Jun 20 04:36:44 CDT 2011


On Sat, Jun 18, 2011 at 10:08:52AM +0200, Arne Babenhauserheide wrote:
> Hi, 
> 
> I just read in the history rewriting/renicing discussion that there now is a way to hide changesets. 
> 
> Did I understand it correctly, that I can add a field to a commit to cause other changesets to be hidden? (searching the wiki only turned up the LiquidHg page)

This is not the intended use. But there is nothing that prevent you to
implement an "hider" using commit (abandon will do it).

> That would make it possible to implement the group extension much more elegantly (currently it uses unelegant monkey-patching of the log - to the point that I did not want to hack on it anymore…).

Then you have to describe how hidden changeset with non-hidden changeset should
behave, convince use and implement the proper log behaviour.

(or join the "obsolete changeset" effort)


-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial/attachments/20110620/4c610a7f/attachment.pgp>


More information about the Mercurial mailing list