From: Chris Mason <chris.mason@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Samuel <chris@csamuel.org>,
"Chris L. Mason" <clmason@fusionio.com>,
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 09:10:14 -0400 [thread overview]
Message-ID: <20120821131014.GA1722@shiny> (raw)
In-Reply-To: <CA+55aFxQiV2iHYQ3NVm=9K=9i6mBo1zwMuvXNrpwnLQwpsRx3A@mail.gmail.com>
On Mon, Aug 20, 2012 at 07:55:59PM -0600, Linus Torvalds wrote:
> On Mon, Aug 20, 2012 at 6:53 PM, Chris Samuel <chris@csamuel.org> wrote:
> >
> > 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 ?
>
> Read my -rc2 release notes.
>
> TL;DR: I rejected big pull requests that didn't convince me. Make a
> damn good case for it, or send minimal fixes instead.
>
> I'm tried of these "oops, what we sent you for -rc1 wasn't ready, so
> here's a thousand lines of changes" crap.
When just the second pull went in, I wasn't sure if it was waiting for
vacation or you felt it was too big, but when I saw rc2 it was pretty
clear.
So I'm working up an rc3 pull with longer explanations. The bulk of my
last pull was send/receive fixes. The rc1 send/recv worked fine for me
on my test box, but larger scale use on well aged filesystems showed
some problems.
It's fair to say send/receive wasn't ready. I did expect some fixes for
rc2 but not that many. More details will be in my pull this afternoon,
but with our current code it is working very well for me.
-chris
prev parent reply other threads:[~2012-08-21 13:10 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
2012-08-21 1:55 ` Linus Torvalds
2012-08-21 3:23 ` Chris Samuel
2012-08-21 13:10 ` 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=20120821131014.GA1722@shiny \
--to=chris.mason@fusionio.com \
--cc=chris@csamuel.org \
--cc=clmason@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).