From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs updates for 2.6.39
Date: Mon, 28 Mar 2011 15:35:14 -0700 [thread overview]
Message-ID: <AANLkTikYvGZHfqCsNOUzBE+24-5Pxxk=t294BfSXJhKs@mail.gmail.com> (raw)
In-Reply-To: <1301312919-sup-1222@think>
On Mon, Mar 28, 2011 at 5:08 AM, Chris Mason <chris.mason@oracle.com> wrote:
>
> Linus, I've pushed out two branches for you, for-linus and
> for-linus-unmerged
Thanks. I took the unmerged one, because I do like to see what's going
on. But I did end up verifying the end result against your merge, and
it ended up identical, so we're all good.
Linus
prev parent reply other threads:[~2011-03-28 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 12:08 [GIT PULL] Btrfs updates for 2.6.39 Chris Mason
2011-03-28 13:25 ` David Sterba
2011-03-29 1:12 ` Li Zefan
2011-03-29 11:32 ` Chris Mason
2011-03-28 22:35 ` Linus Torvalds [this message]
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='AANLkTikYvGZHfqCsNOUzBE+24-5Pxxk=t294BfSXJhKs@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).