[PATCH 6 of 7] strip: introduce a soft strip option

[Augie Fackler]

> On Jan 3, 2019, at 10:23 AM, Pulkit Goyal <7895pulkit at gmail.com> wrote:
> 
> 
> 
> On Thu, Jan 3, 2019 at 4:14 AM Boris Feld <boris.feld at octobus.net> wrote:
> # HG changeset patch
> # User Boris Feld <boris.feld at octobus.net>
> # Date 1539697680 -7200
> #      Tue Oct 16 15:48:00 2018 +0200
> # Node ID a82909c0da7cc07ea1a46690ffc08e45ebc14af6
> # Parent  65488c7d2e933cdb2ab1c36b3887a8a67a24fc60
> # EXP-Topic archived-phase-UX
> # Available At https://bitbucket.org/octobus/mercurial-devel/
> #              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r a82909c0da7c
> strip: introduce a soft strip option
> 
> This is the first user-accessible way to use the archived phase introduced in
> 4.8. This implements a feature implemented during the Stockholm sprint. The
> archived phase behave as stripping, changesets are no longer accessible, but
> pulling/unbundling them will make then reappear. The only notable difference
> is that unlike hard stripping, soft stripping does not affect obsmarkers.

I’m not thrilled with this: I had envisioned the archived state as not full of garbage, but full of things that might merit revisiting some day. When I strip (or prune it) it’s usually a dead end, whereas I’d like a way to say “this isn’t interesting now, but it might be again some day”.

I have no idea if I’m in the minority, and I know this is very late feedback (because of the holidays I haven’t been at a computer much) but hopefully it’s useful.