On 11/08/2016 03:50 AM, Gregory Szorc wrote:
On Mon, Nov 7, 2016 at 4:41 AM, Pierre-Yves David <pierre-yves.da...@ens-lyon.org <mailto:pierre-yves.da...@ens-lyon.org>> wrote: On 11/05/2016 07:26 PM, Gregory Szorc wrote: # HG changeset patch # User Gregory Szorc <gregory.sz...@gmail.com <mailto:gregory.sz...@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?
As for everything else, having "(EXPERIMENTAL)" on the first line should do it.
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
You certainly have buy in the the general idea, I expect many details to be ironed out. A wiki page will allow us to discuss and track many of them:
- Possible targets, - Possible output, - backward compatibility story, - progress tracking, - name discussion (because apparently some people have idea) - etc, Cheers and extra thank for tackling this, -- Pierre-Yves David _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
