Hidden Commits in 4.3

[Durham Goode]

On 4/4/17 6:11 PM, 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://goo.gl/7DJ9AI
>
> If people find this approach promising, I can commit to trying to get
> this upstream by the August release. So if you have questions or
> concerns, please let me know so I can address them.
>
>
> [0] see: "obsolete: track node versions"
> [1] see: "repo: add an ability to hide nodes in an appropriate way"

While I want to focus on the above proposal first, questions may come up 
about how we do evolve in a world where hidden is defined as proposed.

This next Google doc contains a draft of my next proposal. It lays out a 
auto rebase UI that I think could also make it into the August 1st 
release, and that I would also be happy to commit to getting into core.

https://goo.gl/wuP2Vl