From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [RFC] vfs.git (and mount API) status
Date: Sat, 5 Jan 2019 13:33:20 -0800 [thread overview]
Message-ID: <CAHk-=wjkO_iRm_7KdGMqEEboDG3XMHo6DY0d5ex60hFxtrYEQw@mail.gmail.com> (raw)
In-Reply-To: <20190104055958.GL2217@ZenIV.linux.org.uk>
On Thu, Jan 3, 2019 at 10:00 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> First of all, my apologies for being very late with
> any pull requests this window. There had been quite a bit
> of reshuffling (and fixes) in mount API series; see
> vfs.git #Q.. (up to #Q44) for the whole gory story. And yes,
> it is what it looks like - 44 branches with this stuff
> getting massaged.
> In the current form it's not ready for pull as a whole.
> It's in much better shape than it used to be, and I *am* reasonably
> sure it'll get into mergable shape by the next cycle, but right now
> the situation looks thus:
[...]
Ok, I've pulled your two small piles (trivial and mount#1), and they look fine.
And honestly, I'm just as happy to leave the rest for later. I know
the fs option parser changes are going to cause conflicts, I really
don't want to deal with them very late in the merge window.
Particularly if you want to work on some of the parser issues
themselves anyway.
Linus
prev parent reply other threads:[~2019-01-05 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 5:59 [RFC] vfs.git (and mount API) status Al Viro
2019-01-05 21:33 ` Linus Torvalds [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='CAHk-=wjkO_iRm_7KdGMqEEboDG3XMHo6DY0d5ex60hFxtrYEQw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).