[PATCH 4 of 5] obsolete: add allowunstable option

[Durham Goode]

On 10/15/14, 12:21 PM, "Durham Goode" <durham at fb.com> wrote:

>
>
>On 10/15/14, 11:50 AM, "Augie Fackler" <raf at durin42.com> wrote:
>
>>On Tue, Oct 14, 2014 at 02:51:51PM -0700, Durham Goode wrote:
>>> # HG changeset patch
>>> # User Durham Goode <durham at fb.com>
>>> # Date 1413318313 25200
>>> #      Tue Oct 14 13:25:13 2014 -0700
>>> # Node ID 03f3746186c5b5e12dbf81278557297ab4071393
>>> # Parent  70613113a0765b0e7133db0e0bad42a7254b3531
>>> obsolete: add allowunstable option
>>
>>Iiinteresting. Does the end-state of this series look something like
>>histedit being able to force-on "allowunstable" during the histedit
>>process? That'd be *awesome* for things like 'stop'.
>
>Not really.  Histedit could only force allowunstable on if createmarkers
>was already on (a future patch enforces that), which means we couldn¹t
>allow unstable unless the user has already opted in at least somewhat. So
>it doesn¹t buy us much.

Actually, I may have misunderstood your question.  I guess the answer is
maybe.  But a future patch does prevent these options from being on
without createmarkers being on already, so we may want to rethink that if
having individual options enabled is desirable.