[PATCH]

[Idan Kamara]

(please see points 2 and 7 at
http://mercurial.selenic.com/wiki/MailingLists#List_etiquette)

On Sat, Apr 21, 2012 at 8:41 PM, Gregg Lind <gregg.lind at gmail.com> wrote:

> Idan,
>
> Hand-editing the .hg/bisest-state file seems to be the most general
> purpose solution to 'fix problems with a bisect'.  I am not sure that
> exposing every possible command would help.  Even adding the doc
> change that mentions where the file is would help.
>

Yes but you really don't want users to be meddling with that file.

Mentioning .hg/bisect.state in the doc seems harmless (and also
suitable for stable).


>
> On Sat, Apr 21, 2012 at 12:38 PM, Idan Kamara <idankk86 at gmail.com> wrote:
> > On Sat, Apr 21, 2012 at 7:50 PM, Gregg Lind <gregg.lind at gmail.com>
> wrote:
> >>
> >> # HG changeset patch
> >> # User Gregg Lind <gregg.lind at gmail.com>
> >> # Date 1335026469 18000
> >> # Node ID 06e5c2d746430332e82c663526bbd145e62e63e5
> >> # Parent  55982f62651f1974fcd91197f1c4801cc98a48f2
> >> bisect: bisect -d --dump option  (issue1271)
> >
> >
> > You say on the bts that it's hard to recover after mistakenly
> > marking a cset as good/bad but this doesn't seem to help
> > fix that.
> >
> > Perhaps a --rewind option that restores the previous state would
> > be better.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120421/53b3814d/attachment.html>