mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jani Partanen <jiipee@sotapeli.fi>
To: Kent Overstreet <kent.overstreet@linux.dev>,
	Matthew Wilcox <willy@infradead.org>
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 10:49:03 +0300	[thread overview]
Message-ID: <c55affa6-4b8e-4110-bf44-c595d4cda81f@sotapeli.fi> (raw)
In-Reply-To: <5ip2wzfo32zs7uznaunpqj2bjmz3log4yrrdezo5audputkbq5@uoqutt37wmvp>

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.

As I already said like month or 2 back, you are unable to do code and 
communication. You do one well (what I understand from comments, I am 
not a coder myself) and you suck on the other.


It does not help:

- that you are trashing constantly other filesystems.

- that you are bragging that you are here to challenge Linus.

  -that you cannot see your own faults.

- that you are playing the victim when shit hits the fan.


You and I have much same. I am also asshole who will argue for the sake 
of argument. So even when I know that I am wrong, I still keep going and 
that is behavior what I am not proud and I start to be too old that I 
can be fixed. After all, I am always right.

Linus is that kind of person who would really feed my hunger to argue. 
Seems like he works for you also.


Minor stuff I want to point out is that you do fearmongering by telling 
how other filesystems constantly break up and world really need bcachefs 
to save the world. This is quite pointless and stupid marketing. I have 
been running btrfs, ext4 and xfs years, sorry decades in multiple 
systems and I cannot even recall when I had last  time any issues with 
them what wasn't user error or hardware error. I am running even btrfs 
raid-5 on system what is not behind UPS and power outtakes is a thing here.


// Jani


  reply	other threads:[~2025-08-12  7:54 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 15:14 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 [this message]
2025-08-12 10:09               ` Martin Steigerwald
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=c55affa6-4b8e-4110-bf44-c595d4cda81f@sotapeli.fi \
    --to=jiipee@sotapeli.fi \
    --cc=admin@aquinas.su \
    --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

all inboxes | Powered by JetHome®