From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xfs <linux-xfs@vger.kernel.org>
Subject: 4.20 plans
Date: Sat, 22 Sep 2018 18:23:53 -0700 [thread overview]
Message-ID: <20180923012353.GS20086@magnolia> (raw)
Hi all,
I've recovered enough to start reviewing patches and collecting up all
my scattered brains again. Dave will handle the merge window for 4.20
and I'll take over again after -rc1 is out. For this release, we intend
to focus on stability and defer new features until 4.21. In other
words, we'd prefer bug fixes and cleanups only this time around.
It's nice to be back,
--D
reply other threads:[~2018-09-23 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180923012353.GS20086@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.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