Backwards compatibility [was "bisect: track the current changeset"]

[Bryan O'Sullivan]

On Wed, May 2, 2012 at 5:29 PM, Bryan O'Sullivan <bos at serpentine.com> wrote:

> bisect: track the current changeset (issue3382)
>>
>
> This breaks a couple of bisect tests. Don't apply just yet, please.
>

The bisect test that was broken was checking the output of "hg log" with
the template keywords for displaying the bisect state.

I'd changed these from "unknown" and "U" to "current" and "C" to denote the
untested changeset that's currently being visited.

I *think* that the usual response would be that this breaks backwards
compatibility for scripts that parse such output. Assuming that holds, I
believe that those template keywords should go back to their prior
behaviours. But I'm just checking first: Matt, an opinion, please?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120502/ce9fe51b/attachment.html>