From: Andi Kleen <andi@firstfloor.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: current git kernel has strange problems during bisect
Date: Sun, 11 Jan 2009 21:29:20 +0100 [thread overview]
Message-ID: <87tz85fuxr.fsf@basil.nowhere.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0901111113150.6528@localhost.localdomain> (Linus Torvalds's message of "Sun, 11 Jan 2009 11:13:30 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
>
> For bisect purposes, if you know you're not chasing down a btrfs issue,
> you can do
>
> git bisect good 34353029534a08e41cfb8be647d734b9ce9ebff8
Could you perhaps add some standard tag for that commit? That
would make it easier than to always find the exact btrfs commit.
Just an idea.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2009-01-11 20:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 15:02 current git kernel has strange problems during bisect Christian Borntraeger
2009-01-11 15:07 ` Christian Borntraeger
2009-01-11 15:14 ` Johannes Schindelin
2009-01-11 15:20 ` Christian Borntraeger
2009-01-11 16:31 ` Boaz Harrosh
2009-01-11 19:13 ` Linus Torvalds
2009-01-11 19:42 ` Sam Ravnborg
2009-01-11 19:47 ` Alexey Zaytsev
2009-01-11 23:02 ` Pierre Habouzit
2009-01-12 4:51 ` Christian Couder
2009-01-12 5:03 ` Christian Couder
2009-01-11 20:04 ` Linus Torvalds
2009-01-11 21:39 ` Christian Borntraeger
2009-01-11 22:27 ` Daniel Barkalow
2009-01-13 20:26 ` Kyle Moffett
2009-01-15 16:54 ` Andreas Bombe
2009-01-15 23:13 ` Kyle Moffett
2009-01-11 21:54 ` Sam Ravnborg
2009-01-11 22:17 ` Alexey Zaytsev
2009-01-11 22:32 ` Sam Ravnborg
2009-01-11 22:34 ` Daniel Barkalow
2009-01-11 20:29 ` Andi Kleen [this message]
2009-01-11 20:51 ` 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=87tz85fuxr.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=borntraeger@de.ibm.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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