From: Chris Mason <clm@fb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Smaller btrfs pull
Date: Sat, 16 Aug 2014 12:46:42 -0400 [thread overview]
Message-ID: <53EF8AF2.2070605@fb.com> (raw)
In-Reply-To: <CA+55aFz-aSbmLoZv=CGY1bXpQ1zE935-FjTLMZF5=5hteyf9kg@mail.gmail.com>
On 08/16/2014 11:11 AM, Linus Torvalds wrote:
> On Fri, Aug 15, 2014 at 11:26 AM, Chris Mason <clm@fb.com> wrote:
>>
>> I've been running xfstests with these against your current git
>> overnight, but I'm queueing up longer tests as well. I understand
>> you may want to wait until rc2, but either way I'll get a sane queue
>> into my linux-next branch for the rest of the rcs.
>
> You completely mis-understand.
>
> If something isn't appropriate for the merge window, then it sure as
> HELL isn't appropriate for later rc's either.
>
> So I'm not going to pull some "stragglers" later and just pull some
> initial stuff now. That's not how this works.
Hi Linus,
Sorry that I wasn't clear. I had already pushed 1/2 of the commits off
to the 3.18 merge window. Of the remaining commits, my plan was to send
the fixes that would qualify for rc2 or rc3 during those rcs.
I was trying to say that I fully expected these patches to be closely
inspected. I'll bring my white gloves.
-chris
prev parent reply other threads:[~2014-08-16 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 17:26 [GIT PULL] Smaller btrfs pull Chris Mason
2014-08-16 15:11 ` Linus Torvalds
2014-08-16 16:46 ` 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=53EF8AF2.2070605@fb.com \
--to=clm@fb.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).