From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>,
Matthew Wilcox <willy@infradead.org>,
Jani Partanen <jiipee@sotapeli.fi>
Cc: "Aquinas Admin" <admin@aquinas.su>,
"Malte Schröder" <malte.schroeder@tnxip.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Carl E. Thompson" <list-bcachefs@carlthompson.net>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17
Date: Tue, 12 Aug 2025 12:09:03 +0200 [thread overview]
Message-ID: <3374793.44csPzL39Z@lichtvoll.de> (raw)
In-Reply-To: <c55affa6-4b8e-4110-bf44-c595d4cda81f@sotapeli.fi>
Hi Jani, hi.
Jani Partanen - 12.08.25, 09:49:03 CEST:
> On 10/08/2025 2.13, Kent Overstreet wrote:
> > And now, I just got an email from Linus saying "we're now talking
> > about
> > git rm -rf in 6.18", after previously saying we just needed a
> > go-between.
> >
> > So if that's the plan, I need to be arguing forcefully here, because a
> > lot is on the line for a lot of people.
>
> No that is not what you need to do. Arguing is the guarantee way that rm
> -rf will happen.
>
> You need to *SHUT* *THE* *FUCK* *UP* *RIGHT* *NOW!* That is what you
> need to do and find very very fast some spokesman/woman/person who deal
> all the communication.
I might have worded this differently, but in essence I agree.
The likely hood of BCacheFS pull requests being accepted again would have
been far better without that initial comment and subsequent comments from
you, Kent, (and some others) on this thread. Actually I felt that the
thread was even going in a quite good direction, before your first comment
to it. Some users spoke in favor of accepting the pull request. And I feel
after your comment that momentum was completely destroyed. As I read your
first comment, Kent, I thought: Oh no, now this is going to go downhill
just like the other threads about the topic. And unfortunately that
happened. It was predictable. Completely predictable.
And avoidable.
See, Kent, you argued all the time. Look at the results.
Again: Look at your behavior and look at the results. Really do it. Take
time to do it.
It is not even about to what extent your arguments have been accurate or
not. But more about the *way* you argued.
If you continue to do the same thing all over again, you will receive the
same result. (Unless someone in charge changes their behavior in a
significant way, but do you really like to make BCacheFS acceptance in
kernel community dependent on that? You may wait a very long time then.)
See, it is not about right or wrong, but it is about where the lever to
change the outcome actually is. And that lever is not in asking others to
change. And it is also not within insisting that you are right, even in
case you are right at least to some extent.
It may very well be that others overreacted. But it is outside of your
power to change that. Especially not by blaming or asking them to change.
Blaming is a certain way to give away power over what you experience to
someone else.
Step back. Take some time to contemplate about what happened. Actually
that is a good approach for everyone involved, I think.
Seek another approach to communicate *differently* from what you have
already been doing all the time. Then you *might* achieve a different
result.
Doing the same thing over and over again and expecting a different result
is insane.
Best,
--
Martin
next prev parent reply other threads:[~2025-08-12 10:09 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 15:14 [GIT PULL] bcachefs changes for 6.17 Kent Overstreet
2025-08-05 21:19 ` Malte Schröder
2025-08-05 22:41 ` Carl E. Thompson
2025-08-07 12:42 ` Aquinas Admin
2025-08-09 17:36 ` Kent Overstreet
2025-08-09 19:21 ` Josef Bacik
2025-08-09 20:37 ` Kent Overstreet
2025-08-09 21:34 ` Kent Overstreet
2025-08-10 2:24 ` Theodore Ts'o
2025-08-10 3:17 ` Kent Overstreet
2025-08-10 4:05 ` Sasha Levin
2025-08-10 4:13 ` Kent Overstreet
2025-08-10 4:26 ` Gerald B. Cox
2025-08-10 5:17 ` Kent Overstreet
2025-08-10 5:59 ` Theodore Ts'o
2025-08-10 6:51 ` Kent Overstreet
2025-08-10 10:22 ` Martin Steigerwald
2025-08-11 15:48 ` Peanut gallery 2c James Lawrence
2025-08-11 16:08 ` Kent Overstreet
2025-08-11 17:00 ` James Lawrence
[not found] ` <aJsIOj6jbPKayO0s@mayhem.fritz.box>
2025-08-12 16:26 ` Kent Overstreet
2025-08-11 16:48 ` [GIT PULL] bcachefs changes for 6.17 Aquinas Admin
2025-08-10 8:02 ` Martin Steigerwald
2025-08-10 6:05 ` Carl E. Thompson
2025-08-11 16:02 ` Aquinas Admin
2025-08-11 16:09 ` Kent Overstreet
2025-08-09 23:01 ` Matthew Wilcox
2025-08-09 23:13 ` Kent Overstreet
2025-08-12 7:49 ` Jani Partanen
2025-08-12 10:09 ` Martin Steigerwald [this message]
2025-08-11 9:51 ` Konstantin Shelekhin
2025-08-11 14:26 ` Kent Overstreet
2025-08-11 18:13 ` Carl E. Thompson
2025-08-11 18:40 ` Malte Schröder
2025-08-12 0:44 ` Carl E. Thompson
2025-08-11 18:48 ` Aquinas Admin
2025-08-11 19:42 ` Martin Steigerwald
2025-08-11 21:04 ` Konstantin Shelekhin
2025-08-12 1:08 ` Kent Overstreet
2025-08-12 6:52 ` asdx
2025-08-12 7:04 ` Kent Overstreet
2025-08-12 7:17 ` asdx
2025-08-12 19:35 ` Keith Busch
2025-08-12 20:03 ` Kent Overstreet
2025-08-12 20:30 ` Keith Busch
2025-08-12 20:31 ` Kent Overstreet
2025-08-12 20:38 ` Keith Busch
2025-08-12 20:45 ` Kent Overstreet
2025-08-12 20:54 ` Keith Busch
2025-08-12 20:57 ` Kent Overstreet
2025-08-11 16:45 ` Aquinas Admin
2025-08-10 4:29 ` Gerhard Wiesinger
2025-08-07 14:27 ` Martin Steigerwald
2025-08-07 17:29 ` Peter Schneider
2025-08-10 6:20 ` Gerhard Wiesinger
2025-08-10 10:32 ` Martin Steigerwald
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=3374793.44csPzL39Z@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=admin@aquinas.su \
--cc=jiipee@sotapeli.fi \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list-bcachefs@carlthompson.net \
--cc=malte.schroeder@tnxip.de \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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