From: Chris Samuel <chris@csamuel.org>
To: Chris Mason <chris.mason@fusionio.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Btrfs List <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL 1/2] Btrfs fixes
Date: Tue, 21 Aug 2012 11:53:45 +1000 [thread overview]
Message-ID: <5032EA29.2060002@csamuel.org> (raw)
In-Reply-To: <20120809155029.GA29278@shiny>
On 10/08/12 01:50, Chris Mason wrote:
> Hi everyone,
>
> This first pull is the bulk of our changes for the next rc. It is
> against the 3.5 kernel so people testing the new features have a stable
> point to work against. This was tested against Linus' current tree as
> well.
[...]
This pull request with a whole heap of btrfs fixes (46 commits) appears
not to have been merged yet, does anyone know if it was rejected or just
missed ?
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2012-08-21 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 15:50 [GIT PULL 1/2] Btrfs fixes Chris Mason
2012-08-21 1:53 ` Chris Samuel [this message]
2012-08-21 1:55 ` Linus Torvalds
2012-08-21 3:23 ` Chris Samuel
2012-08-21 13:10 ` Chris Mason
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=5032EA29.2060002@csamuel.org \
--to=chris@csamuel.org \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).