From: Jiri Slaby <jirislaby@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Commit Links [was: Linux 6.17-rc5]
Date: Mon, 13 Oct 2025 10:53:36 +0200 [thread overview]
Message-ID: <81e33495-ad29-49b1-bb45-ee44f9f2a5ce@kernel.org> (raw)
In-Reply-To: <CAHk-=wju1GO-AdGHag2v94mXdmg2uaFez5R8YE2js7ngn+hJyg@mail.gmail.com>
On 13. 09. 25, 0:22, Linus Torvalds wrote:
> On Thu, 11 Sept 2025 at 23:24, Jiri Slaby <jirislaby@kernel.org> wrote:
>> OK, can we have Submitted-at: or something for the above which you could
>> completely ignore?
>
> No.
>
> We're not adding garbage that I'm "supposed to ignore".
>
> Stop this idiotic thread. Stop adding crap automatically.
Pardon me? I understand you are tired of this (so am I), but can we stay
constructive instead of constantly resistive? This is not helping.
> I have made it very clear that you can add "Link" to your submissions
> as long as IT IS NOT SOME AUTOMATIC MEANINGLESS GARBAGE.
Yes, that's why I proposed something different than Link:.
> I have also pointed out that you can find the original submission in
> various much better ways than the meaningless link think you argue
> for.
Obvious question: how? Do you have some power tool which we all are
missing?
One example for all: for 23743ba64709, I want to get the applied v2
20250825125607.2478-3-calixte.pernot@grenoble-inp.org and not mistakenly
resent v3 20250909202629.9386-2-calixte.pernot@grenoble-inp.org. How do
I do that (if there was not a Link)? I can look up for tons of these
false pos/negs.
Seeming solutions: people are adding git-notes for some trees (tip,
Vasant's tree). People are implementing b4 dig. People are using lore
search. All those approaches are hopeless as they simply do NOT work as
Link does. [Some maintainers I talked to inside SUSE are going to keep
_this kind_ of Link (but I guess you will start refusing their PRs
eventually).]
My stance: if I bisect to a commit which does not yield me the right
message-id in a second, I won't report it and stop right there. I am not
going to burn my time by dubious searching here and there. The same as
you don't want to burn your time clicking only-for-you-useless Links --
only viewed from the opposite side. And well, provided I alone upgrade
the Tumbleweed kernel when a new release comes, I have to find bugs in
final releases quite often.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-10-13 8:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 22:25 Linux 6.17-rc5 Linus Torvalds
2025-09-09 0:50 ` Guenter Roeck
2025-09-09 15:27 ` Brian Norris
2025-09-12 6:24 ` Commit Links [was: Linux 6.17-rc5] Jiri Slaby
2025-09-12 19:14 ` Al Viro
2025-09-12 22:22 ` Linus Torvalds
2025-10-13 8:53 ` Jiri Slaby [this message]
2025-09-15 8:16 ` Uwe Kleine-König
2025-09-15 16:22 ` Sean Christopherson
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=81e33495-ad29-49b1-bb45-ee44f9f2a5ce@kernel.org \
--to=jirislaby@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.