Re: [PATCH] bisect reset: Allow resetting to any commit, not just a branch
- From
Johannes Sixt <j.sixt@viscovery.net>
- Date
- Oct 13, 2009, 06:45 UTC
- Message-ID
- <4AD42203.6030802@viscovery.net>
- In-Reply-To
- <7vaazw6uyi.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
Show 7 quoted lines
> I would understand it, if not agreeing that I also am often in that > situation myself", if somebody does not even care which commit he was on > before starting the bisection, but knows (or is willing to decide at that > point) which branch (or even a specific commit, while still being > detached) he wants to switch to. And it would make sense to avoid an > extra checkout that snaps back to the pre-bisection commit before > switching to the new state he has chosen.
The situation that I'm faced quite frequently is that after I find a regression, I cannot tell which released version did not have the breakage. Hence, the first thing I have to do is to find a good commit. Therefore, I jump around in ancient history until I find a good commit. Then I start bisect. I certainly do NOT want to be warped back to this ancient commit by 'bisect reset'.
-- Hannes