From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@kernel.org, tools@linux.kernel.org
Subject: Re: In defense of Link (was Re: [b4] initial "b4 dig" to supplant Link: trailers)
Date: Mon, 13 Oct 2025 19:09:49 -0400 [thread overview]
Message-ID: <20251013190418-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=whSShtPG1_+02Cc4yDuEJxVqX=G8tAx0gW7UjA7cuBp-w@mail.gmail.com>
Thanks Linus!
One note:
On Mon, Oct 13, 2025 at 10:00:01AM -0700, Linus Torvalds wrote:
...
> Because we *HAVE* automated information that is already sufficient.
> Every single commit already fundamentally has sufficient information
> to find the submission if it was to a lore-tracked mailing list:
>
> - patch ID
>
> - commit date
>
> - subject line and patch date (note: maybe from the email, maybe in
> the body of the email)
>
> - author name and email (note again: might be the email 'from', but
> might well be the 'body of the email' From: line)
Well I for one would often ask the contributor to repost
modifying just the commit message.
The only thing distinguishing posts then is the date?
Doesn't it seem somewhat fragile, to rely on date?
E.g. thinkably someone can post an old version of my patch (e.g. include
in their patchset) and at the same time I happen to
post one with an updated commit log.
Now what?
As a maintainer, I also sometimes squash two patches together, what then?
--
MST
next prev parent reply other threads:[~2025-10-13 23:09 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 5:59 In defense of Link (was Re: [b4] initial "b4 dig" to supplant Link: trailers) Paolo Bonzini
2025-10-11 6:13 ` Willy Tarreau
2025-10-11 6:33 ` Paolo Bonzini
2025-10-15 8:56 ` Geert Uytterhoeven
2025-10-11 6:39 ` Jiri Slaby
2025-10-11 10:33 ` Mark Brown
2025-10-12 23:27 ` Jason Gunthorpe
2025-10-13 8:18 ` Vlastimil Babka (SUSE)
2025-10-13 8:27 ` Paolo Bonzini
2025-10-13 8:42 ` Willy Tarreau
2025-10-13 8:48 ` Jiri Slaby
2025-10-13 8:56 ` Willy Tarreau
2025-10-13 11:21 ` Laurent Pinchart
2025-10-13 14:26 ` [workflows]Re: " Steven Rostedt
2025-10-13 14:39 ` Laurent Pinchart
2025-10-13 14:59 ` Steven Rostedt
2025-10-13 15:04 ` Laurent Pinchart
2025-10-13 15:44 ` Steven Rostedt
2025-10-13 11:03 ` Mark Brown
2025-10-13 11:49 ` James Bottomley
2025-10-13 12:15 ` Mark Brown
2025-10-13 12:29 ` Paolo Bonzini
2025-10-13 12:47 ` James Bottomley
2025-10-13 13:02 ` Jürgen Groß
2025-10-15 18:05 ` Jeff Johnson
2025-10-16 16:47 ` Linus Torvalds
2025-10-13 12:21 ` Michael S. Tsirkin
2025-10-13 17:00 ` Linus Torvalds
2025-10-13 18:14 ` Paolo Bonzini
2025-10-13 18:53 ` Linus Torvalds
2025-10-13 20:12 ` Junio C Hamano
2025-10-13 21:44 ` Linus Torvalds
2025-10-13 23:22 ` Sasha Levin
2025-10-14 1:29 ` Linus Torvalds
2025-10-14 3:39 ` Willy Tarreau
2025-10-16 14:52 ` Geert Uytterhoeven
2025-10-16 15:08 ` Jason Gunthorpe
2025-10-16 15:33 ` Geert Uytterhoeven
2025-10-13 22:31 ` Paolo Bonzini
2025-10-14 6:47 ` Jiri Slaby
2025-10-13 21:59 ` Theodore Ts'o
2025-10-13 23:09 ` Michael S. Tsirkin [this message]
2025-10-14 1:23 ` Linus Torvalds
2025-10-14 10:38 ` Michael S. Tsirkin
2025-10-14 16:56 ` Linus Torvalds
2025-10-14 18:05 ` Luck, Tony
2025-10-14 18:41 ` Linus Torvalds
2025-10-14 19:09 ` Paolo Bonzini
2025-10-14 21:10 ` Jason Gunthorpe
2025-10-15 7:37 ` Geert Uytterhoeven
2025-10-15 7:33 ` Geert Uytterhoeven
2025-10-15 9:38 ` Miguel Ojeda
2025-10-15 12:11 ` Mark Brown
2025-10-15 13:50 ` James Bottomley
2025-10-15 13:59 ` Jürgen Groß
2025-10-15 15:08 ` Mark Brown
2025-10-15 15:14 ` Peter Zijlstra
2025-10-15 15:18 ` [workflows]Re: " Steven Rostedt
2025-10-15 15:53 ` Peter Zijlstra
2025-10-15 15:59 ` Steven Rostedt
2025-10-15 16:06 ` Peter Zijlstra
2025-10-15 16:15 ` Steven Rostedt
2025-10-15 16:43 ` Mark Brown
2025-10-15 16:15 ` Vlastimil Babka (SUSE)
2025-10-15 16:44 ` Steven Rostedt
2025-10-15 16:58 ` Konstantin Ryabitsev
2025-10-16 9:28 ` Matthieu Baerts
2025-10-15 17:01 ` Miguel Ojeda
2025-10-15 18:40 ` Laurent Pinchart
2025-10-16 7:32 ` Peter Zijlstra
2025-10-16 8:20 ` Vlastimil Babka (SUSE)
2025-10-16 13:58 ` Steven Rostedt
2025-10-15 14:37 ` Miguel Ojeda
2025-10-15 14:50 ` [workflows]Re: " Steven Rostedt
2025-10-15 13:51 ` Martin K. Petersen
2025-10-15 14:16 ` Konstantin Ryabitsev
2025-10-15 14:42 ` Miguel Ojeda
2025-10-15 15:03 ` Jason Gunthorpe
2025-10-15 14:55 ` [workflows]Re: " Steven Rostedt
2025-10-15 17:34 ` Martin K. Petersen
2025-10-15 14:51 ` Geert Uytterhoeven
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=20251013190418-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=konstantin@linuxfoundation.org \
--cc=pbonzini@redhat.com \
--cc=tools@linux.kernel.org \
--cc=torvalds@linuxfoundation.org \
--cc=users@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 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.