From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Greg KH <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
dan.j.williams@intel.com, Doug Anderson <dianders@chromium.org>,
"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: Replacing Link trailers
Date: Thu, 16 Oct 2025 15:36:07 +0100 [thread overview]
Message-ID: <0f5607e8-b0a0-460b-ad38-c9539a6523e8@sirena.org.uk> (raw)
In-Reply-To: <20251016-vehement-kittiwake-of-joy-d6db8e@lemur>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Thu, Oct 16, 2025 at 09:00:49AM -0400, Konstantin Ryabitsev wrote:
> I recommend that we all stop beating the Link: trailer topic and sit on our
> hands until the above is either accepted or rejected by the git maintainers.
> IOW:
> - Keep current "mindless" Link: approach, with the patch.msgid.link domain for
> automatically-added Link: trailers. It mitigates the problem of Linus
> getting annoyed at the ambiguity, but keeps things working for maintainers
> who are already dependent on these links being present.
> - Work with git maintainers to add commit provenance information into the
> commit headers.
> - Reconvene at the upcoming maintainer summit to hammer out whatever remains
> of the discussion.
> Would that work for everyone?
This seems sensible to me.
I will note that as a Debian stable user I'm expecting to get a new
version of git in roughly 2027, though I imagine there will be backports
available.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-10-16 14:36 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 11:53 James Bottomley
2025-10-13 12:25 ` Mathieu Desnoyers
2025-10-13 12:48 ` James Bottomley
2025-10-13 12:50 ` Mark Brown
2025-10-13 14:52 ` Guenter Roeck
2025-10-13 17:36 ` Steven Rostedt
2025-10-14 19:12 ` Johannes Berg
2025-10-14 19:35 ` Steven Rostedt
2025-10-15 22:01 ` Johannes Berg
2025-10-15 22:22 ` Steven Rostedt
2025-10-16 10:16 ` Simona Vetter
2025-10-16 12:18 ` Hans de Goede
2025-10-16 18:39 ` David Woodhouse
2025-10-16 7:43 ` Geert Uytterhoeven
2025-10-14 20:23 ` Doug Anderson
2025-10-16 8:08 ` Dan Carpenter
2025-10-13 15:40 ` Doug Anderson
2025-10-13 16:31 ` James Bottomley
2025-10-13 17:39 ` Steven Rostedt
2025-10-13 17:50 ` Theodore Ts'o
2025-10-13 19:07 ` H. Peter Anvin
2025-10-13 19:20 ` Linus Torvalds
2025-10-13 19:35 ` James Bottomley
2025-10-13 19:37 ` H. Peter Anvin
2025-10-13 19:36 ` H. Peter Anvin
2025-10-13 20:34 ` Doug Anderson
2025-10-13 20:36 ` H. Peter Anvin
2025-10-13 20:58 ` Laurent Pinchart
2025-10-13 20:59 ` Vlastimil Babka
2025-10-13 21:46 ` Doug Anderson
2025-10-14 14:23 ` Sasha Levin
2025-10-14 11:09 ` Mark Brown
2025-10-13 19:35 ` H. Peter Anvin
2025-10-14 16:01 ` dan.j.williams
2025-10-14 17:46 ` Greg KH
2025-10-14 17:57 ` dan.j.williams
2025-10-15 17:09 ` dan.j.williams
2025-10-15 17:55 ` James Bottomley
2025-10-15 18:04 ` Luck, Tony
2025-10-15 18:37 ` Konstantin Ryabitsev
2025-10-15 19:13 ` dan.j.williams
2025-10-15 19:15 ` Linus Torvalds
2025-10-15 19:17 ` Linus Torvalds
2025-10-15 22:51 ` Doug Anderson
2025-10-16 4:26 ` Chen-Yu Tsai
2025-10-16 6:57 ` Greg KH
2025-10-16 10:04 ` Jani Nikula
2025-10-16 11:54 ` James Bottomley
2025-10-16 12:18 ` Greg KH
2025-10-16 12:29 ` James Bottomley
2025-10-16 13:00 ` Konstantin Ryabitsev
2025-10-16 13:47 ` Steven Rostedt
2025-10-16 14:36 ` Mark Brown [this message]
2025-10-16 14:58 ` Rob Herring
2025-10-16 15:07 ` James Bottomley
2025-10-16 15:36 ` Geert Uytterhoeven
2025-10-16 15:52 ` James Bottomley
2025-10-16 15:37 ` Steven Rostedt
2025-10-16 19:29 ` H. Peter Anvin
2025-10-16 19:32 ` James Bottomley
2025-10-16 23:53 ` H. Peter Anvin
2025-10-16 19:09 ` James Bottomley
2025-10-17 2:27 ` Doug Anderson
2025-10-17 8:44 ` Vlastimil Babka
2025-10-17 9:21 ` Geert Uytterhoeven
2025-10-17 10:09 ` Rafael J. Wysocki
2025-10-16 12:34 ` Mathieu Desnoyers
2025-10-16 12:49 ` Mark Brown
2025-10-16 12:49 ` Geert Uytterhoeven
2025-10-16 12:54 ` Mathieu Desnoyers
2025-10-16 13:07 ` Geert Uytterhoeven
2025-10-16 12:51 ` Jiri Kosina
2025-10-16 12:54 ` James Bottomley
2025-10-16 13:51 ` Steven Rostedt
2025-10-16 16:21 ` Michael S. Tsirkin
2025-10-16 12:20 ` Steven Rostedt
2025-10-15 21:29 ` Kees Cook
2025-10-15 21:40 ` Mark Brown
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=0f5607e8-b0a0-460b-ad38-c9539a6523e8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dan.j.williams@intel.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox