How to hide a changeset by committing in another one?
Kevin Bullock
kbullock+mercurial at ringworld.org
Mon Jun 20 11:23:09 CDT 2011
(moving thread to mercurial-devel)
On Jun 20, 2011, at 4:36 AM, Pierre-Yves David wrote:
> On Sat, Jun 18, 2011 at 10:08:52AM +0200, Arne Babenhauserheide wrote:
>> 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)
I think Arne is getting at something different here, namely reimplementing the group extension (with all of, and only, its current behavior) using the new 'hidden' facility.
Arne, as far as I know the only documentation is the changesets themselves, namely for your purposes: <http://www.selenic.com/hg/rev/7e295dd10d40> and <http://www.selenic.com/hg/rev/f3a40fd7008c>.
Looks like your extension would just add grouped changesets to the changelog.hiddenrevs list in the wrapped `log` command.
pacem in terris / mir / shanti / salaam / heiwa
Kevin R. Bullock
More information about the Mercurial-devel
mailing list