From: Brendan Jackman <jackmanb@google.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/2] checkpatch: Add support for Checkpatch-ignore patch footer
Date: Wed, 15 Jan 2025 10:58:31 +0100 [thread overview]
Message-ID: <CA+i-1C2-xB7BT-A786GSKhnZo0ucbk1m4=kPOBJ5fBempRZL4w@mail.gmail.com> (raw)
In-Reply-To: <20250114-olivine-adder-of-weather-1eaabf@meerkat>
On Tue, 14 Jan 2025 at 20:26, Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> On Tue, Jan 14, 2025 at 07:29:14PM +0100, Brendan Jackman wrote:
> > is that something people really complain about?
>
> Yes, I expect Linus will reject commits that carry that trailer on the exact
> grounds that I brought up.
Oh OK, Linus is definitely people.
In that case I'll go for the graveyard+git-notes approach. Thanks for the input!
BTW, I also thought of just forgetting the graveyard thing and just
having checkpatch look directly at the Git notes when run in --git
mode. I thought maybe everyone uses --git mode in practice, but I
checked and b4 doesn't seem to. So it's worth making this work for raw
patches too.
next prev parent reply other threads:[~2025-01-15 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 16:04 [PATCH 0/2] " Brendan Jackman
2025-01-13 16:04 ` [PATCH 1/2] " Brendan Jackman
2025-01-13 19:15 ` Joe Perches
2025-01-14 11:42 ` Brendan Jackman
2025-01-14 11:43 ` Brendan Jackman
2025-01-14 13:34 ` Konstantin Ryabitsev
2025-01-14 14:25 ` Brendan Jackman
2025-01-14 16:04 ` Konstantin Ryabitsev
2025-01-14 18:29 ` Brendan Jackman
2025-01-14 19:26 ` Konstantin Ryabitsev
2025-01-15 9:58 ` Brendan Jackman [this message]
2025-01-13 16:04 ` [PATCH 2/2] docs: checkpatch: Document " Brendan Jackman
2025-01-13 16:20 ` [PATCH 0/2] checkpatch: Add support for " Matthew Wilcox
2025-01-13 17:11 ` Brendan Jackman
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='CA+i-1C2-xB7BT-A786GSKhnZo0ucbk1m4=kPOBJ5fBempRZL4w@mail.gmail.com' \
--to=jackmanb@google.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=workflows@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