From: Christoph Hellwig <hch@infradead.org>
To: Darrick Wong <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: Re: 2019 NYE Patchbomb Guide!
Date: Wed, 15 Jan 2020 07:12:19 -0800 [thread overview]
Message-ID: <20200115151219.GA9817@infradead.org> (raw)
In-Reply-To: <6b5080eb-cb85-4504-a13b-bf9d90e4ad0d@default>
On Tue, Dec 31, 2019 at 05:25:08PM -0800, Darrick Wong wrote:
> Hi folks,
>
> It's still the last day of 2019 in the US/Pacific timezone, which means
> it's time for me to patchbomb every new feature that's been sitting
> around in my development trees! As you know, all of my development
> branches are kept freshly rebased on the latest Linus kernel so that I
> can send them all at a moment's notice. Once a year I like to dump
> everything into the public archives to increase XFS' bus factor.
It seems like you missed the stale data exposure fix series using
unwritten extents in buffered writeback. Can we get that one off the
back burner?
next prev parent reply other threads:[~2020-01-15 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 1:25 2019 NYE Patchbomb Guide! Darrick Wong
2020-01-15 15:12 ` Christoph Hellwig [this message]
2020-01-15 16:34 ` Darrick J. Wong
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=20200115151219.GA9817@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--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