From: Luis Chamberlain <mcgrof@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Theodore Ts'o <tytso@mit.edu>,
Adam Manzanares <a.manzanares@samsung.com>,
Tyler Hicks <code@tyhicks.com>,
linux-xfs <linux-xfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATH 5.10 0/4] xfs stable candidate patches for 5.10.y (part 1)
Date: Fri, 27 May 2022 08:40:14 -0700 [thread overview]
Message-ID: <YpDw3uVFB7LjPquX@bombadil.infradead.org> (raw)
In-Reply-To: <CAOQ4uxgc9Zu0rvTY3oOqycGG+MoYEL3-+qghm9_qEn67D8OukA@mail.gmail.com>
On Fri, May 27, 2022 at 03:24:02PM +0300, Amir Goldstein wrote:
> On Fri, May 27, 2022 at 12:08 PM Dave Chinner <david@fromorbit.com> wrote:
> > Backport candidate: yes. Severe: absolutely not.
> In the future, if you are writing a cover letter for an improvement
> series or internal pull request and you know there is a backport
> candidate inside, if you happen to remember to mention it, it would
> be of great help to me.
Amir, since you wrote a tool enhancement to scrape for possible
candidates, *if* we defined some sort of meta-data to describe
this sort of stuff on the cover letter:
Backport candidate: yes. Severe: absolutely not
It would be useful when scraping. Therefore, leaving the effort
to try to backport / feasibility to others. This would be different
than a stable Cc tag, as those have a high degree of certainty.
How about something like:
Backport-candidate: yes
Impact: low
Luis
next prev parent reply other threads:[~2022-05-27 15:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 11:17 [PATH 5.10 0/4] xfs stable candidate patches for 5.10.y (part 1) Amir Goldstein
2022-05-25 11:17 ` [PATH 5.10 1/4] xfs: detect overflows in bmbt records Amir Goldstein
2022-05-25 11:17 ` [PATH 5.10 2/4] xfs: show the proper user quota options Amir Goldstein
2022-05-25 11:17 ` [PATH 5.10 3/4] xfs: fix the forward progress assertion in xfs_iwalk_run_callbacks Amir Goldstein
2022-05-25 11:17 ` [PATH 5.10 4/4] xfs: fix an ABBA deadlock in xfs_rename Amir Goldstein
2022-05-26 17:27 ` [PATH 5.10 0/4] xfs stable candidate patches for 5.10.y (part 1) Darrick J. Wong
2022-05-26 18:44 ` Luis Chamberlain
2022-05-26 18:59 ` Amir Goldstein
2022-05-27 13:10 ` Luis Chamberlain
2022-05-26 18:47 ` Amir Goldstein
2022-05-27 6:06 ` Christoph Hellwig
2022-05-27 7:01 ` Amir Goldstein
2022-05-27 9:08 ` Dave Chinner
2022-05-27 12:24 ` Amir Goldstein
2022-05-27 15:40 ` Luis Chamberlain [this message]
2022-05-27 17:19 ` Darrick J. Wong
2022-05-27 23:42 ` Dave Chinner
2022-05-28 5:00 ` Amir Goldstein
2022-06-01 4:31 ` Dave Chinner
2022-06-01 7:10 ` Amir Goldstein
2022-06-02 4:12 ` Theodore Ts'o
2022-06-02 5:34 ` Amir Goldstein
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=YpDw3uVFB7LjPquX@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=amir73il@gmail.com \
--cc=code@tyhicks.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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).