All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Theodore Ts'o <tytso@mit.edu>,
	Steven Rostedt <rostedt@goodmis.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: Replacing Link trailers
Date: Mon, 13 Oct 2025 23:58:57 +0300	[thread overview]
Message-ID: <20251013205857.GA28892@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAD=FV=UjA8+pZoXMh9WgCHZAUX=pd7ehWxuu9kTFr5Dp5O-rCQ@mail.gmail.com>

On Mon, Oct 13, 2025 at 01:34:05PM -0700, Doug Anderson wrote:
> On Mon, Oct 13, 2025 at 12:20 PM Linus Torvalds wrote:
> > On Mon, 13 Oct 2025 at 12:07, H. Peter Anvin wrote:
> > >
> > > This was the *original* definition that I proposed, which was vetoed by Linus because it didn't provide a clickable experience.
> >
> > Yeah., I still don't believe that Message-ID is any better than a link.
> >
> > And the only believable argument *for* this all is the "one-click experience".
> >
> > Because I still believe that "if you use tools, then 'b4 dig' is
> > better than *any* pointless tag that just is entirely redundant and
> > only cuts down on the available information".
> >
> > So the one-click argument actually resonates with me, even if that is
> > very obviously not the workflow I use. At least I *understand* that
> > argument.
> >
> > All the other arguments seem just disingenuous in that they literally
> > give less useful information than "b4 dig" does.
> 
> Wow, I hadn't heard of "b4 dig" and it doesn't appear to have landed
> yet. ...but I searched and it was easy to find a reference. I'll check
> it out. Oh, it's using AI. I guess my suggestion that we should use AI
> to solve this problem was more on point than I realized. ;-) ;-) ;-)
> 
> OK, I found Sasha's RFC [1].

I think the one discussed in this mail thread is the implementation from
Konstantin, available from
https://git.kernel.org/pub/scm/utils/b4/b4.git/.

> The first thing I note is that "b4 dig" takes a Message-Id as an
> argument. So now I'm confused. I must be misunderstanding the problem
> we're trying to solve with the "Link:" tag?!
> 
> From how I've used it, the "Link" tag allows you to start with a
> commit hash in Linux and then go from there to a mailing list post
> (and/or Message-Id). ...and then it was suggested that we don't need a
> "Link" tag (or anything containing "Message-Id") because "b4 dig"
> solves the problem. ...but then "b4 dig" needs a Message-Id to work?
> Eh?
> 
> [1] https://lore.kernel.org/all/20250909163214.3241191-1-sashal@kernel.org/

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2025-10-13 20:59 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 11:53 Replacing Link trailers 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 [this message]
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=20251013205857.GA28892@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dianders@chromium.org \
    --cc=hpa@zytor.com \
    --cc=ksummit@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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.