From: Christoph Hellwig <hch@infradead.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Dave Chinner <david@fromorbit.com>,
Greg KH <gregkh@linuxfoundation.org>,
stable <stable@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dave Chinner <dchinner@redhat.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
"Luis R. Chamberlain" <mcgrof@kernel.org>
Subject: Re: XFS patches for stable
Date: Sun, 2 Dec 2018 08:10:16 -0800 [thread overview]
Message-ID: <20181202161016.GA27696@infradead.org> (raw)
In-Reply-To: <20181202152547.GI221015@sasha-vm>
As someone who has done xfs stable backports for a while I really don't
think the autoselection is helpful at all. Someone who is vaguely
familiar with the code needs to manually select the commits and QA them,
which takes a fair amount of time, but just needs some manual help if it
should work ok.
I think we are about ready to have a new xfs stable maintainer lined up
if everything works well fortunately.
next prev parent reply other threads:[~2018-12-02 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181129060110.159878-1-sashal@kernel.org>
[not found] ` <20181129060110.159878-25-sashal@kernel.org>
[not found] ` <20181129121458.GK19305@dastard>
[not found] ` <20181129124756.GA25945@kroah.com>
[not found] ` <20181129224019.GM19305@dastard>
[not found] ` <20181130082203.GA26830@kroah.com>
[not found] ` <20181130101441.GA213156@sasha-vm>
2018-11-30 20:35 ` [PATCH AUTOSEL 4.14 25/35] iomap: sub-block dio needs to zeroout beyond EOF Darrick J. Wong
[not found] ` <20181130215005.GP19305@dastard>
[not found] ` <20181201074909.GC213156@sasha-vm>
2018-12-01 9:09 ` XFS patches for stable Amir Goldstein
2018-12-02 15:25 ` Sasha Levin
2018-12-02 16:10 ` Christoph Hellwig [this message]
2018-12-02 20:08 ` Greg KH
2018-12-03 14:41 ` Richard Weinberger
2018-12-03 16:56 ` Sasha Levin
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=20181202161016.GA27696@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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