From: Theodore Tso <tytso@mit.edu>
To: Parag Warudkar <parag.lkml@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 14354] Re: ext4 increased intolerance to unclean shutdown?
Date: Fri, 16 Oct 2009 09:06:38 -0400 [thread overview]
Message-ID: <20091016130638.GA8196@mit.edu> (raw)
In-Reply-To: <20091016091558.GA10184@mit.edu>
On Fri, Oct 16, 2009 at 05:15:58AM -0400, Theodore Tso wrote:
> These are three commits that seem most likely, but there are
> only 93 ext4-related commits, so doing a "git bisect start v2.6.31
> v2.6.32-rc5 -- fs/ext4 fs/jbd2"
One correction. The git bsect start usage is:
git bisect start [<bad> [<good>...]] [--] [<paths>...]
So the correct git bisect start command should be:
git bisect start v2.6.32-rc5 v2.6.31 -- fs/ext4 fs/jbd2
And similarly, "git bisect start v2.6.31 v2.6.31-rc3" should have been:
git bisect start v2.6.31-rc3 v2.6.31
My apologies for any confusion.
- Ted
next prev parent reply other threads:[~2009-10-16 14:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 4:28 ext4 increased intolerance to unclean shutdown? Parag Warudkar
2009-10-16 6:31 ` Maxim Levitsky
2009-10-16 9:15 ` [Bug 14354] " Theodore Tso
2009-10-16 13:06 ` Theodore Tso [this message]
2009-10-16 19:16 ` Ric Wheeler
2009-10-25 6:22 ` Pavel Machek
2009-10-26 13:49 ` Ric Wheeler
2009-10-16 22:24 ` Parag Warudkar
2009-10-16 22:24 ` Parag Warudkar
2009-10-26 15:42 ` Linus Torvalds
2009-10-27 10:15 ` Aneesh Kumar K.V
2009-10-29 20:10 ` Mingming
2009-10-29 21:25 ` Parag Warudkar
2009-10-29 21:25 ` Parag Warudkar
2009-10-29 21:38 ` Eric Sandeen
2009-10-30 8:16 ` Theodore Tso
2009-10-30 13:54 ` Eric Sandeen
2009-10-30 13:54 ` Eric Sandeen
2009-10-30 19:56 ` Andreas Dilger
2009-10-31 9:15 ` Theodore Tso
2009-10-31 15:24 ` Aneesh Kumar K.V
2009-10-31 15:24 ` Aneesh Kumar K.V
2009-10-29 21:42 ` Theodore Tso
2009-10-29 21:42 ` Theodore Tso
2009-10-29 21:52 ` Parag Warudkar
2009-10-29 21:52 ` Parag Warudkar
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=20091016130638.GA8196@mit.edu \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.lkml@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.