Ezio Melotti added the comment:
I agree with Antoine, but mentioning hg update is a good idea so I changed that.
--
assignee: -> ezio.melotti
resolution: wont fix -> fixed
stage: -> committed/rejected
status: open -> closed
type: -> enhancement
___
Roundup Robot added the comment:
New changeset 24c2cfee3b06 by Ezio Melotti in branch 'default':
#19311: mention hg update in the bisect faq.
http://hg.python.org/devguide/rev/24c2cfee3b06
--
nosy: +python-dev
status: pending -> open
___
Python tracke
Antoine Pitrou added the comment:
I don't think we want the devguide to become a Mercurial manual.
Also, it is easy to get help for a Mercurial command: just type "hg help
bisect".
--
nosy: +pitrou
resolution: -> wont fix
status: open -> pending
___
New submission from Martin Matusiak:
The offending section:
http://docs.python.org/devguide/faq.html#how-do-i-find-which-changeset-introduced-a-bug-or-regression
I think this could be improved a bit. The key point is that "hg bisect
--bad/good" is a command relative to the checked out changeset
