From: "Ted Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 fixes for 3.1-rc5
Date: Wed, 31 Aug 2011 17:42:33 -0400 [thread overview]
Message-ID: <20110831214233.GA6666@thunk.org> (raw)
In-Reply-To: <CA+55aFzFRo0vmuED2wbab6ZU9oH4Rriav6R13zGNtUnS2UStMA@mail.gmail.com>
On Wed, Aug 31, 2011 at 11:25:58AM -0700, Linus Torvalds wrote:
> On Wed, Aug 31, 2011 at 10:46 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > Please pull from:
> >
> > git://github.com/tytso/ext4.git for_linus-20110831 # 8c0bec2151a
> >
> > to get the following bug fix. It address a lockdep warning which a lot
> > of people have been complaining about.
>
> So what's up? Bad English and a github address makes me unhappy.
>
> I can imagine that you decided not to use kernel.org due to hera being
> down, but this still makes me want to say "please more references".
Yes, I decided to use github because master.kernel.org is down.
for_linus-20110831 is a signed tag, which you can verify.
Sorry for the bad english, I was doing too many other things at the
same time when I was composing the pull request. The pull should
consist of a single commit to fix a Lockddep complain; see:
https://bugzilla.kernel.org/show_bug.cgi?id=41682
I just realized I forgot to include the BZ URL in the commit
description; sigh, sorry about that. Would you prefer that I ammend
the commit and send you a new pull request?
- Ted
next prev parent reply other threads:[~2011-08-31 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 17:46 [GIT PULL] ext4 fixes for 3.1-rc5 Theodore Ts'o
2011-08-31 18:25 ` Linus Torvalds
2011-08-31 18:47 ` Arnaud Lacombe
2011-08-31 18:57 ` Arnaud Lacombe
2011-08-31 21:42 ` Ted Ts'o [this message]
2011-09-03 18:17 ` Ted Ts'o
2011-09-03 19:20 ` Linus Torvalds
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=20110831214233.GA6666@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@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