Hidden Commits in 4.3

[Ryan McElroy]

On 4/5/17 2:11 AM, Durham Goode wrote:
> I would like to formally propose a new pattern for dealing with hidden 
> commits, along with the concrete steps to getting it enabled in core 
> by default by the August release.
>
> The proposal is quite concise, so check out this 1-page Google doc for 
> the details and to comment:
>
> https://goo.gl/7DJ9AI
>

Much of this thread (and various subthreads and VC chats) has gone down 
the path of rehashing the same arguments for and against one type of 
hiding vs another. After chatting with most of the people expressing 
strong opinions here, I believe we will not resolve these disagreements 
with more replies and examples. While I happen to still believe that 
this proposal and changeset evolution are not mutually exclusive, some 
people seem to disagree with me on this.

The limited specific feedback on the proposed plan was incorporated into 
the above-linked Google Doc. Since it has been unchanged for a while, I 
turned it into a Plan wiki page:

https://www.mercurial-scm.org/wiki/HideUnhidePlan

Note that I cleaned up a few things:

* s/commit/changeset (except when referring to the commit command)
* Trivial cleanups to unclear language
* Small softening of some language that I felt was too strong given the 
data we have.

I think the next step is for the community to officially figure out if 
this is a good direction to go in, however that happens.

Cheers,

~Ryan