From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Benjamin Tissoires <bentiss@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jiri Kosina <jikos@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] HID for 6.11
Date: Mon, 22 Jul 2024 09:58:18 -0400 [thread overview]
Message-ID: <20240722-marvellous-talented-magpie-ef4ca9@lemur> (raw)
In-Reply-To: <3610ec4c-524a-4cd7-93a9-16023618a49d@kernel.org>
On Mon, Jul 22, 2024 at 03:32:48PM GMT, Krzysztof Kozlowski wrote:
> > this commit broke b4 for everyone starting next-20240719, as it's
> > an empty cover letter with b4 tracking information
>
> Konrad gave me idea which could at least protect final tree from such
> mistakes - commit hook for merges, something like:
>
> https://github.com/krzk/tools/blob/master/linux/verify_b4.sh
> https://github.com/krzk/tools/blob/master/linux/git-hooks-post-merge
I'll include something like this into the contrib section.
Unfortunately, I'm not sure we can ever completely avoid this, but perhaps
linux-next can add a check to see if any of the commits in a merge contain
"--b4-submit-tracking--" and then refuse to consider it?
-K
next prev parent reply other threads:[~2024-07-22 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:34 [GIT PULL] HID for 6.11 Benjamin Tissoires
2024-07-18 0:29 ` Linus Torvalds
2024-07-18 1:27 ` pr-tracker-bot
2024-07-22 12:46 ` Konrad Dybcio
2024-07-22 12:51 ` Krzysztof Kozlowski
2024-07-22 12:56 ` Krzysztof Kozlowski
2024-07-22 13:51 ` Benjamin Tissoires
2024-07-22 13:59 ` Benjamin Tissoires
2024-08-06 22:04 ` Jacob Keller
2024-07-22 13:32 ` Krzysztof Kozlowski
2024-07-22 13:58 ` Konstantin Ryabitsev [this message]
2024-07-22 18:17 ` Konstantin Ryabitsev
2024-07-23 11:26 ` Konrad Dybcio
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=20240722-marvellous-talented-magpie-ef4ca9@lemur \
--to=konstantin@linuxfoundation.org \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.