[PATCH 2 of 2] commands: introduce `hg display`

Gregory Szorc gregory.szorc at gmail.com
Mon Nov 7 22:50:34 EST 2016


On Mon, Nov 7, 2016 at 4:41 AM, Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:

> On 11/05/2016 07:26 PM, Gregory Szorc wrote:
>
>> # HG changeset patch
>> # User Gregory Szorc <gregory.szorc at gmail.com>
>> # Date 1478370119 25200
>> #      Sat Nov 05 11:21:59 2016 -0700
>> # Node ID 0ebc1e627383bdf017f509a60725c0b39d6d40d9
>> # Parent  4bce42e7330311b58ecd38a4acbcd2d2dd1351ba
>> commands: introduce `hg display`
>>
>
> I've not looked into this in details yet¹, but is looks like it should be
> flagged (EXPERIMENTAL) and having some plan page could be useful.


I'm fine marking it as experimental. How do you want that done?

Regarding the plan page, this proposed command was discussed and had buy-in
at the 4.0 Sprint. I believe the commit message captures most of the
important details of that discussion.

I'm not sure what benefit a wiki page will provide. If it is capturing
planned display views, I can list those here:

* Things we have read-only commands for today (tags, branches, bookmarks,
possibly qseries)
* inprogress/smartlog/wip/unfinished (whatever we call it)
* stack
* Anything else people think of
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20161107/13ead594/attachment.html>


More information about the Mercurial-devel mailing list