[PATCH] localrepo: better error message with obsmarkers but no evolve

[Augie Fackler]

On Thu, Sep 10, 2015 at 9:53 AM, Jordi Gutiérrez Hermoso
<jordigh at octave.org> wrote:
> On Thu, 2015-09-10 at 09:42 -0400, Augie Fackler wrote:
>> Obsolete markers are very useful without evolve - you can enable them
>> and get nice performance wins for things like histedit and rebase. The
>> error message in core should talk about obsolete markers, not
>> evolve.
>
> Hm... how do you create obsolete commits without evolve? I didn't
> know you could do that.

...with rebase? or histedit? All you have to do is turn evolve on.

>
> Come to think of it, why is this a warning at all? Obsolete commits
> are already hidden without evolve, so what's the problem?

I think if obsolete is disabled then the markers aren't loaded and
you'll see your dead changesets (and presumably there will be red in
the camera frame somewhere.)