From: Jonathan Corbet <corbet@lwn.net>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] orangefs filesystem
Date: Sat, 8 Aug 2015 16:37:10 -0600 [thread overview]
Message-ID: <20150808163710.058d2723@lwn.net> (raw)
In-Reply-To: <CAOg9mSRpssBYVgJkFyBhxXGM-Qheeq1tC+E8MA7qqdT7m1m1ig@mail.gmail.com>
On Sat, 8 Aug 2015 11:26:52 -0400
Mike Marshall <hubcap@omnibond.com> wrote:
> Paying attention to LWN is a good way to become
> aware of when the merge window opens, right?
We'll let you know :) But the real key is to watch for the 4.2 release,
which is likely to happen on the 16th or the 23rd.
> What has seemed counter-intuitive to me, as
> the maintainer of an out-of-tree filesystem, is
> that I should work to be ready for the merge window, but
> since that's when new features show up, that also might be
> when I'll find out about changes like dropping .read and
> .write from file_operations or changing readdir to iterate...
That's what linux-next is for. If your filesystem is working there,
there should not be any surprises for you during the merge window.
jon
prev parent reply other threads:[~2015-08-08 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 18:39 [GIT PULL] orangefs filesystem Mike Marshall
2015-08-07 20:44 ` Andrew Morton
2015-08-07 23:02 ` Mike Marshall
2015-08-08 1:24 ` Linus Torvalds
2015-08-08 15:26 ` Mike Marshall
2015-08-08 22:37 ` Jonathan Corbet [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=20150808163710.058d2723@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).