From: "Reece Dunn" <msclrhd@googlemail.com>
To: Git <git@vger.kernel.org>
Subject: git bisect start on a tag revision fails
Date: Sun, 10 Feb 2008 11:01:33 +0000 [thread overview]
Message-ID: <3f4fd2640802100301y436bda41kcca1b1eb8ec0ea10@mail.gmail.com> (raw)
Hi,
When hunting bugs with the wine source code
(git://source.winehq.org/git/wine.git), both Dan Kegel and I have
found the following berhaviour with git bisect:
$ git checkout wine-0.9.54
HEAD is now at 8f954cc... Release 0.9.54.
$ git bisect start
fatal: ref HEAD is not a symbolic ref
Bad HEAD - I need a symbolic ref
Whereas doing:
$ git checkout master
$ git bisect start
then:
$ git checkout wine-0.9.54
$ git bisect good
works.
Is it possible to have bisect support non-symbolic refs?
- Reece
next reply other threads:[~2008-02-10 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 11:01 Reece Dunn [this message]
2008-02-10 13:59 ` [PATCH] bisect: allow starting with a detached HEAD Johannes Schindelin
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=3f4fd2640802100301y436bda41kcca1b1eb8ec0ea10@mail.gmail.com \
--to=msclrhd@googlemail.com \
--cc=git@vger.kernel.org \
/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).