From: Josef Bacik <josef@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs updates for 3.1
Date: Sat, 02 Jul 2011 17:25:20 -0400 [thread overview]
Message-ID: <4E0F8CC0.8010909@redhat.com> (raw)
In-Reply-To: <4E0E3091.9060704@redhat.com>
On 07/01/2011 04:39 PM, Josef Bacik wrote:
> Hey Chris,
>
> Since I'm going on vacation next week I wanted to get everything ready for you
> in case you get bored with fsck and want to put together a 3.1 tree :). If you
> can pull
>
> git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git for-chris
>
> It is based on your for-linus branch. Here is the shortlog and diffstat
>
Ugh sorry I had to update the don't panic patch because I'm an idiot.
Thanks,
Josef
next prev parent reply other threads:[~2011-07-02 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 20:39 [GIT PULL] Btrfs updates for 3.1 Josef Bacik
2011-07-02 21:25 ` Josef Bacik [this message]
2011-07-11 0:20 ` Mitch Harder
2011-07-11 13:33 ` Josef Bacik
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=4E0F8CC0.8010909@redhat.com \
--to=josef@redhat.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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).