Rewriting changeset order on push/pull (keeping the history graph tidy)

[Waldemar Augustyn]

On 08/12/2012 10:58 PM, Sean Farley wrote:
>> What would be very useful is a way of "hiding" the complicated history.
>> It can still exist, but it would be nice if there was a simple way of
>> "annotating" the history so that it becomes easier to inspect.
>>
>> Does anything like this currently exist?
> Only experimentally, but this kind of thing is partially possible with
> the Obsolete / Evolve extension:
>
> http://mercurial.selenic.com/wiki/ChangesetsObsolescence
>
> Warning: I'm serious about the experimental part.
I probably mentioned that once or twice before but I think the term
"obsolescence" is really unfortunate and should be changed. Perhaps a
better term would be "views"??  What is desired is to create another
level of history management where certain portions of the history tree
would not be visible (with some options to force, etc., perhaps with
authentication).  This does not mean that these portions would become
"obsolete", it just means that they should not be looked at.  There are
several reasons other than true obsolescence for doing that.  Further,
the wire  protocol should be extended to allow fetching only portions
that are visible.