Hidden Commits in 4.3

[Durham Goode]

On 4/5/17 2:28 AM, Simon Farnsworth wrote:
> On 05/04/2017 02:11, Durham Goode wrote:
>> There's been a lot of discussion about how to hide and unhide commits
>> lately [0][1], and I feel the complexity of our current approach is
>> hurting our ability to reason about it, making it impossible to make
>> progress.
>>
>> 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://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_7DJ9AI&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=mEgSWILcY4c4W3zjApBQLA&m=cTl6eEfd0SyhW5M6ZM65eJ2ZldOrwdJ_KM0pKS9tZ5M&s=T30BYaK4BkpV_DBoFTcWZm0_VGBJG0FEHA5jUJqcxXw&e=
>>
>>
>
> Is there any reason why this is a Google Doc, not a HiddenCommitsPlan on
> the mercurial-scm.org wiki?

I was hoping people would comment on specific sections, so we could have 
threaded discussions before committing it to a more permanent wiki page.