From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fscrypt@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bug fixes for 4.13
Date: Mon, 7 Aug 2017 09:55:13 -0400 [thread overview]
Message-ID: <20170807135513.6d4d2z6uv52f4pki@thunk.org> (raw)
In-Reply-To: <CA+55aFz+_-KRuOHRrOaaTYGcUgWtn4aFm=C4sUCtGRs8BBgJMw@mail.gmail.com>
On Sun, Aug 06, 2017 at 12:39:23PM -0700, Linus Torvalds wrote:
> On Sun, Aug 6, 2017 at 12:27 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > A large number of ext4 bug fixes and cleanups for v4.13
>
> A couple of these appear to be neither cleanups nor fixes. And a lot
> of them appear to be very recent.
>
> I've pulled this, but if I hear about problems, ext4 is going to be on
> my shit-list, and you'd better be a *lot* more careful about pull
> requests. Because this is not ok.
Sorry, I'll be conservative in sending pull requests to you in the
future. The one commit that wasn't a bug fix, cleanup, or prereq for
a bugfix/cleanup was an optimization for a feature that landed during
this merge window (large xattrs using xattr inodes).
The patches did go through a full regression test cycle, and
everything was reviewed by at least a second person, but yeah, -rc4 is
getting a bit late in the cycle. I certainly wouldn't have sent it
any later...
- Ted
prev parent reply other threads:[~2017-08-07 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 19:27 Theodore Ts'o
2017-08-06 19:39 ` Linus Torvalds
2017-08-07 13:55 ` Theodore Ts'o [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=20170807135513.6d4d2z6uv52f4pki@thunk.org \
--to=tytso@mit.edu \
--cc=linux-fscrypt@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
all inboxes | Powered by JetHome®