Re: Replacing Link trailers

[James Bottomley <James.Bottomley@HansenPartnership.com>]

On Thu, 2025-10-16 at 17:36 +0200, Geert Uytterhoeven wrote:
> Hi James,
> 
> On Thu, 16 Oct 2025 at 17:07, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > On Thu, 2025-10-16 at 09:58 -0500, Rob Herring wrote:
> > [...]
> > > With a new atom_type, there doesn't seem to be a simple way to
> > > turn on or off a field in git-log. We'd need '--pretty=linus' or
> > > some new git config setting.
> > 
> > Well, not on a per field basis, no.  --pretty=raw will give you
> > everything, though and "grep ^message-id" would pull it out, which
> > I think would work for scripts.  If humans want to use it, I think,
> > per Linus, we'd have some option to convert it to a clickable
> > something.
> 
> Let's hope bug reporters who barely learnt how to run git bisect will
> manage to find it...

Do those type of bug reporters even know how to use Link: today?  But
regardless the point of this is to solve the tooling mechanical issue,
not to build something that should be visible to everyone.  As I said,
if we split the discussion into the mechanical do for everything part
(which this is) the rest is a discussion of what additional information
and how should we add to the commit body.

Regards,

James