stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: fs/bcachefs/
Date: Tue, 16 Jan 2024 12:26:38 -0500	[thread overview]
Message-ID: <2ve257m37wusszvzkr254hp62nvxecmdcnybmft5ebl6n7hesj@yelqgrderuay> (raw)
In-Reply-To: <2024011614-modify-primer-65dd@gregkh>

On Tue, Jan 16, 2024 at 03:13:08PM +0100, Greg KH wrote:
> On Mon, Jan 15, 2024 at 05:12:17PM -0500, Kent Overstreet wrote:
> > Hi stable team - please don't take patches for fs/bcachefs/ except from
> > myself; I'll be doing backports and sending pull requests after stuff
> > has been tested by my CI.
> 
> Now done:
> 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=9bf1f8f1ca9ae53cf3bc8781e4efdb6ebaee70db
> 
> We will ignore it for any "Fixes:" tags, or AUTOSEL, but if you
> explicitly add a "cc: stable@" in the signed-off-by area, we will pick
> that up.

Would it work for your process to ignore cc: stable@ as well?

I want a tag that I can have tooling grep for later that means "this
patch should be backported later, after seeing sufficient testing", and
cc: stable@ has that meaning in current usage.

Or if you'd like that to be reserved for yourself we could think of a
new one.

> 
> > Thanks, and let me know if there's any other workflow things I should
> > know about
> 
> This is going to cause you more work, but less for us, so thanks!

per our conversation on IRC I'm going to write some simple tooling for
grepping through the git log for patches that may want to be backported
and haven't yet made it to a stable tree.

Also, Sasha, is there any reason your autosel tool couldn't be made
available for others to use that way?

Yes, it's more work for myself, but I have strong opinions that I as the
person who knows the code ought to be picking the patches to backport,
and doing the backports and resolving merge conflicts when necessary;
but collaborating on tooling would be _fantastic_.

  reply	other threads:[~2024-01-16 17:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 22:12 fs/bcachefs/ Kent Overstreet
2024-01-15 23:03 ` fs/bcachefs/ Sasha Levin
2024-02-20 17:23   ` fs/bcachefs/ Kent Overstreet
2024-02-20 18:03     ` fs/bcachefs/ Greg KH
2024-02-20 18:53       ` fs/bcachefs/ Greg KH
2024-02-20 20:06         ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:19           ` fs/bcachefs/ Greg KH
2024-02-20 20:22             ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:39               ` fs/bcachefs/ Greg KH
2024-02-20 20:42                 ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:39             ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:51               ` fs/bcachefs/ Greg KH
2024-02-20 21:00                 ` fs/bcachefs/ Kent Overstreet
2024-02-21 14:53                   ` fs/bcachefs/ Greg KH
2024-02-21 16:00                     ` fs/bcachefs/ Oleksandr Natalenko
2024-02-21 17:57                       ` fs/bcachefs/ Greg KH
2024-02-21 18:10                         ` fs/bcachefs/ Vlastimil Babka
2024-02-21 20:52                           ` fs/bcachefs/ Kent Overstreet
2024-02-21 22:58                           ` fs/bcachefs/ Sasha Levin
2024-02-21 23:12                             ` fs/bcachefs/ Kent Overstreet
2024-02-22  5:48                               ` fs/bcachefs/ Greg KH
2024-02-22  6:30                                 ` fs/bcachefs/ Kent Overstreet
2024-02-22 11:54                                   ` fs/bcachefs/ Sasha Levin
2024-02-21 23:47                             ` fs/bcachefs/ Oleksandr Natalenko
2024-02-22 19:19                           ` stable-kernel-rules was fs/bcachefs/ Pavel Machek
2024-02-22 22:33                             ` Kent Overstreet
2024-02-23 18:50                               ` Pavel Machek
2024-02-20 19:36     ` fs/bcachefs/ Sasha Levin
2024-01-16 14:13 ` fs/bcachefs/ Greg KH
2024-01-16 17:26   ` Kent Overstreet [this message]
2024-01-16 17:44     ` fs/bcachefs/ Greg KH

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=2ve257m37wusszvzkr254hp62nvxecmdcnybmft5ebl6n7hesj@yelqgrderuay \
    --to=kent.overstreet@linux.dev \
    --cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).