From: Greg KH <gregkh@linuxfoundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Subject: Re: fs/bcachefs/
Date: Tue, 20 Feb 2024 19:53:04 +0100 [thread overview]
Message-ID: <2024022007-buggy-operator-2dc5@gregkh> (raw)
In-Reply-To: <2024022056-monkhood-fossil-ec02@gregkh>
On Tue, Feb 20, 2024 at 07:03:23PM +0100, Greg KH wrote:
> On Tue, Feb 20, 2024 at 12:23:33PM -0500, Kent Overstreet wrote:
> > On Mon, Jan 15, 2024 at 06:03:11PM -0500, Sasha Levin 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.
> > > >
> > > > Thanks, and let me know if there's any other workflow things I should
> > > > know about
> > >
> > > Sure, we can ignore fs/bcachefs/ patches.
> >
> > I see that you even acked this.
> >
> > What the fuck?
>
> Accidents happen, you were copied on those patches. I'll go drop them
> now, not a big deal.
Wait, why are you doing "Fixes:" with an empty tag in your commits like
1a1c93e7f814 ("bcachefs: Fix missing bch2_err_class() calls")?
That's messing with scripts and doesn't make much sense. Please put a
real git id in there as the documentation suggests to.
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-20 18:53 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 ` Greg KH [this message]
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 ` fs/bcachefs/ Kent Overstreet
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=2024022007-buggy-operator-2dc5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--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