From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Anders Kaseorg <andersk@MIT.EDU>, git@vger.kernel.org
Subject: Re: [PATCH] bisect reset: Allow resetting to any commit, not just a branch
Date: Tue, 13 Oct 2009 08:45:23 +0200 [thread overview]
Message-ID: <4AD42203.6030802@viscovery.net> (raw)
In-Reply-To: <7vaazw6uyi.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> 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
next prev parent reply other threads:[~2009-10-13 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:38 [PATCH] bisect reset: Allow resetting to any commit, not just a branch Anders Kaseorg
2009-10-12 21:06 ` Junio C Hamano
2009-10-12 21:31 ` Anders Kaseorg
2009-10-12 23:41 ` Junio C Hamano
2009-10-13 6:45 ` Johannes Sixt [this message]
2009-10-13 7:21 ` Junio C Hamano
2009-10-13 7:03 ` Anders Kaseorg
2009-10-13 15:22 ` [PATCH v2] " Anders Kaseorg
2009-10-13 20:06 ` Christian Couder
2009-10-13 20:09 ` Anders Kaseorg
2009-10-13 20:30 ` Christian Couder
2009-10-13 21:02 ` [PATCH v3] " Anders Kaseorg
2009-10-14 9:13 ` Junio C Hamano
2009-10-13 6:39 ` [PATCH] " Johannes Sixt
2009-10-13 7:01 ` Junio C Hamano
2009-10-13 7:45 ` Johannes Sixt
2009-10-13 8:33 ` Junio C Hamano
2009-10-13 14:29 ` Anders Kaseorg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD42203.6030802@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=andersk@MIT.EDU \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).