From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <t-itoh@jp.fujitsu.com>
Subject: Re: [GIT PULL] Btrfs pull -- part 1
Date: Tue, 1 Apr 2014 20:17:05 -0400 [thread overview]
Message-ID: <533B5701.4030303@fb.com> (raw)
In-Reply-To: <533ACC62.1080701@fb.com>
On 04/01/2014 10:25 AM, Chris Mason wrote:
> Hi Linus,
>
> We still have some corruption fixes and other patches coming in for the
> merge window, but this batch is tested and ready to go.
>
> Please pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git master
Tsutomu noticed I put the wrong branch name in. I've pushed my
for-linus over to my master branch so they all match the shortlog and
diffstat below.
Thanks,
Chris
prev parent reply other threads:[~2014-04-02 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 14:25 [GIT PULL] Btrfs pull -- part 1 Chris Mason
2014-04-02 0:17 ` Chris Mason [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=533B5701.4030303@fb.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).