public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Tony Vroon <tony@linx.net>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	"Langsdorf, Mark" <mark.langsdorf@amd.com>
Subject: Re: 2.6.31-07068-g43c1266 Early boot exception
Date: Mon, 21 Sep 2009 14:13:50 -0700	[thread overview]
Message-ID: <4AB7EC8E.80708@zytor.com> (raw)
In-Reply-To: <1253561749.2934.47.camel@localhost>

Tony Vroon wrote:
> On Mon, 2009-09-21 at 12:26 -0700, H. Peter Anvin wrote:
>> Could you please do a git bisect on this problem?
> 
> Would love to, but how do I convert g99bc470 to a correct git revision
> number please?
> 
> chainsaw@prometheus /cvs/linux-2.6 $ git bisect start
> chainsaw@prometheus /cvs/linux-2.6 $ git bisect bad
> chainsaw@prometheus /cvs/linux-2.6 $ git bisect good g99bc470
> fatal: Needed a single revision
> Bad rev input: g99bc470
> 

Drop the leading "g" (which stands for git).

	-hpa


  parent reply	other threads:[~2009-09-21 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 19:14 2.6.31-07068-g43c1266 Early boot exception Tony Vroon
2009-09-21 19:26 ` H. Peter Anvin
2009-09-21 19:35   ` Tony Vroon
2009-09-21 19:36     ` Ingo Molnar
2009-09-21 21:13     ` H. Peter Anvin [this message]
2009-09-21 20:47   ` Tony Vroon
2009-09-22  9:08     ` Tejun Heo
2009-09-22  9:23       ` Arjan van de Ven
2009-09-22 11:40         ` Tejun Heo
2009-09-22 19:36       ` Tony Vroon
2009-09-23  5:52         ` Tejun Heo
2009-09-23  9:19           ` Tony Vroon
2009-09-23  9:23             ` Tejun Heo
2009-09-23 15:46               ` H. Peter Anvin
2009-09-23 23:25                 ` Tejun Heo
2009-09-24  0:05         ` Tejun Heo
2009-09-21 19:53 ` 2.6.31-0.1-default-07068-g43c1266 lockdep warning and scheduling while atomic BUG Henk Martijn
2009-09-21 20:04   ` Oliver Neukum
2009-09-21 20:17     ` Henk Martijn

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=4AB7EC8E.80708@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mingo@elte.hu \
    --cc=tony@linx.net \
    /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