ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: Re: Replacing Link trailers
Date: Thu, 16 Oct 2025 00:01:38 +0200	[thread overview]
Message-ID: <c311cf11f2e0bc2046c428e398508010c7626855.camel@sipsolutions.net> (raw)
In-Reply-To: <20251014153521.693907a1@gandalf.local.home>

On Tue, 2025-10-14 at 15:35 -0400, Steven Rostedt wrote:
> On Tue, 14 Oct 2025 21:12:33 +0200
> Johannes Berg <johannes@sipsolutions.net> wrote:
> 
> > And we're taking it away because literally *one* person thinks that it
> > adds irrelevant noise.
> 
> Are you suggesting that we lost the "benevolent" in our "benevolent dictator"?
> 
>   ;-)

So I'm supposed to be on vacation this week, but this is haunting me I
guess ... I see your ";-)", but I'll respond anyway.

Yes. Yes, in this particular instance I am absolutely saying that.

To me, there's a sort of underlying (social) contract in all of Linux
etc. - yes, we want/need Linus to enforce the things that make for
unpopular reading in the press (say kicking out bcachefs for a recent
example), but we also trust him to "read the room" (so to speak) and
mostly at least, form an opinion informed by the rough consensus. At
least that's my interpretation of how this all works. Call me deluded if
you like. (Seriously, tell me, even in private messages.)

Here, however, we have the exact opposite. Pretty much everyone in the
threads disagrees and prefers a tag in some form (be it link, message-
id, or something else), and yet Linus insists he's right to be annoyed
and impose his will on everyone. Some people in the threads want to find
technological workarounds for his whims, but really all those are just
that: workarounds, and demonstrably don't work as well.

It's not even a technical problem/discussion, if it were, we'd be
reading messages that take the concerns of those people who currently
rely on the link tags seriously, and try to find solutions that work for
everyone. I'm sure we could think of any number of things, even encoding
the message-id in the git commit object format (so it's invisible with
default git log/show format) itself would probably work pretty easily.
But no, instead we read all about how those people are all wrong and
misguided, and how the patch that got applied isn't special [1]. In
other contexts, we'd probably call this "mansplaining", but here we
somehow are supposed to not only tolerate but celebrate, presumably for
the great technological advancement it brings. [2]

[1] seriously? even if it were posted 100 times identically, the one
that got applied would be made special by the very act of being picked
up by the maintainer

[2] b4 dig is (probably) nice, and Linus will likely somehow manage to
have it interpreted that it was because of his actions that it came
about, although it really wasn't his vision but rather his pettiness
that got it started.


So really, I think this has become purely an ego/power dynamics thing,
far detached from any practical reality. _Not_ clicking a link really
isn't that difficult, and distinguishing between "I've modified a patch
so it needs a link now" and "a lookup by patch-id will succeed so no
link is needed" has now become fig-leaf for the naked emperor. It adds
useless work for everyone, not to mention wasting server cycles to do a
search and all that, all because one guy desperately needed to be right.

(But yes, I'm sure that now that everyone is so entrenched, big ego will
win.)

So yeah, circling back to "benevolent" -- for me, this has definitely
broken the "benevolent" part and a lot of trust. But that's fine, I can
also do a job that heavily resolves around following a manager's
arbitrary whims. But my heart won't be in it.

johannes

  reply	other threads:[~2025-10-15 22:01 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 [this message]
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
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=c311cf11f2e0bc2046c428e398508010c7626855.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit@lists.linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox