public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
	Carlos Maiolino <cem@kernel.org>,
	linux-xfs@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the xfs tree
Date: Tue, 11 Feb 2025 14:31:59 -0800	[thread overview]
Message-ID: <20250211223159.GF3028674@frogsfrogsfrogs> (raw)
In-Reply-To: <20250212082141.26dc0ad8@canb.auug.org.au>

On Wed, Feb 12, 2025 at 08:21:41AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   bc0651d93a7b ("xfs: fix online repair probing when CONFIG_XFS_ONLINE_REPAIR=n")
> 
> Fixes tag
> 
>   Fixes: 48a72f60861f79 ("xfs: don't complain about unfixed metadata when repairs were injected")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject
>     Just use
>         git log -1 --format='Fixes: %h ("%s")'
> 
> maybe you meant
> 
> Fixes: 48a72f60861f ("xfs: refactor repair forcing tests into a repair.c helper")
> 
> or
> 
> Fixes: 8336a64eb75c ("xfs: don't complain about unfixed metadata when repairs were injected")

Yes, 8336a64eb75c.

This patch has been on the list for a month now, and nobody complained.
Probably because people aren't good at distinguishing one sequence of
hexadecimal from another.

Could we /please/ have a bot to warn about these annotation problems
when patches are on the list for review, rather than a month later after
it finally enters for-next, without any of the authors, reviewers, or
maintainers having noticed?

Maybe the rest of you are all excellent at this, and I should just fuck
off and quit.

--D

> -- 
> Cheers,
> Stephen Rothwell



  reply	other threads:[~2025-02-11 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 21:21 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2025-02-11 22:31 ` Darrick J. Wong [this message]
2025-02-12 15:52   ` Carlos Maiolino
  -- strict thread matches above, loose matches on Subject: below --
2025-12-17 21:06 Stephen Rothwell
2025-12-18  5:09 ` Christoph Hellwig
2024-10-08 20:06 Stephen Rothwell
2023-09-19  7:25 Stephen Rothwell
2023-06-05  4:22 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2020-04-16 22:19 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2019-08-12 21:45 Stephen Rothwell
2019-01-29 20:56 Stephen Rothwell
2019-01-29 22:08 ` Dave Chinner
2019-01-29 23:06   ` Stephen Rothwell
2019-01-29 23:43     ` Dave Chinner
2019-01-30  0:02       ` Stephen Rothwell
2019-01-30  0:38         ` Dave Chinner

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=20250211223159.GF3028674@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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