From: Doug Anderson <dianders@chromium.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: "ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: Replacing Link trailers
Date: Mon, 13 Oct 2025 08:40:43 -0700 [thread overview]
Message-ID: <CAD=FV=VK0OLj5ASxtUZAUEK1WTxDW9LwCR+yBEKD6AdUyWkNNA@mail.gmail.com> (raw)
In-Reply-To: <a7878386f3546ba475cdf7250ab4f5a6af2a1676.camel@HansenPartnership.com>
Hi,
On Mon, Oct 13, 2025 at 4:53 AM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> There has been a lot of discussion on the tooling list about how the
> loss of link trailers has updated both tooling and triaging issues.
> Konstantin has proposed a tool to get around this, but while that's in
> development, I propose a discussion about making Link (or some
> alternative tag) into the pointer that would work for everyone.
A few random ideas to throw out there:
1. Could we submit a change to the "git" tool to allow something like
the "Link" tag but hide it from the default settings? I'm thinking
something like how "git" only shows the Author/AuthorDate by default
until you say "--format=fuller" and then it also shows you the
Commit/CommitDate. Then we just tell Linus to keep the setting off and
everyone is happy.
2. Given how "everyone" thinks AI is the best thing ever, could AI
help the patch trackers find the version history of the patch / links
to old versions? So when you click on a Link it takes you someplace
where AI has already found links to all the old patches and perhaps
even summarized the mailing list discussion? Maybe this is a terrible
idea and we'd all get flamed the moment the AI gives some bad info,
but somehow it seemed wrong to not suggest an AI solution in this day
and age. :-P
3. Could folks somehow just stage an intervention and tell Linus that
he's wrong and just has to accept the Link tag that he finds useless?
;-) (Hi Linus! I'm sure you're not reading this, right?) While I
certainly can't consider my opinion to hold much weight, it sure seems
like quite a few prominent people in the community find the Link tag
very useful and are sad to see it go. Given all the people that find
the tag useful, it kinda feels like it could stay? Even if Linus has a
10:1 or 100:1 vote in the topic, from what I gather keeping the "Link"
tag would still win (assuming people that don't give a crap just
abstain instead of voting "no"). Not that this is a democracy or
anything...
-Doug
next prev parent reply other threads:[~2025-10-13 15:41 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 [this message]
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
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='CAD=FV=VK0OLj5ASxtUZAUEK1WTxDW9LwCR+yBEKD6AdUyWkNNA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ksummit@lists.linux.dev \
/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