public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: asdx <asdx52@cock.li>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Konstantin Shelekhin <k.shelekhin@ftml.net>,
	admin@aquinas.su, linux-bcachefs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	list-bcachefs@carlthompson.net, malte.schroeder@tnxip.de,
	torvalds@linux-foundation.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17
Date: Tue, 12 Aug 2025 04:17:07 -0300	[thread overview]
Message-ID: <9e81bbfd-1688-46bd-bf38-252fed3b1c82@cock.li> (raw)
In-Reply-To: <rabpjlpydnsnlkrgqmolvgg5tyo2kk5v45evwdt6ffetsqynfy@dt2r3cxio5my>


On 8/12/25 4:04 AM, Kent Overstreet wrote:
> On Tue, Aug 12, 2025 at 03:52:39AM -0300, asdx wrote:
>> On 8/11/25 11:26 AM, Kent Overstreet wrote:
>>> On Mon, Aug 11, 2025 at 12:51:11PM +0300, Konstantin Shelekhin wrote:
>>>>>    Yes, this is accurate. I've been getting entirely too many emails from Linus about
>>>>> how pissed off everyone is, completely absent of details - or anything engineering
>>>>> related, for that matter.
>>>> That's because this is not an engineering problem, it's a communication problem. You just piss
>>>> people off for no good reason. Then people get tired of dealing with you and now we're here,
>>>> with Linus thinking about `git rm -rf fs/bcachesfs`. Will your users be happy? Probably not.
>>>> Will your sponsors be happy? Probably not either. Then why are you keep doing this?
>>>>
>>>> If you really want to change the way things work go see a therapist. A competent enough doctor
>>>> probably can fix all that in a couple of months.
>>> Konstantin, please tell me what you're basing this on.
>>>
>>> The claims I've been hearing have simply lacked any kind of specifics;
>>> if there's people I'd pissed off for no reason, I would've been happy to
>>> apologize, but I'm not aware of the incidences you're claiming - not
>>> within a year or more; I have made real efforts to tone things down.
>>>
>> You keep lying. How can you be so cynical? Just two days ago you were
>> complaining on #bcache about how much control Linus has over Linux and there
>> was a lot of talk about getting him removed from Linux via CoC action.
> Are you the same guy who was just posting this on Phoronix? Either
> you're trolling, or you misread something.
>
> For the record, I'm one of the more anti CoC people out there - I agree
> with the spirit of their goals, not so much the approach. I would never
> invoke them on anyone; I prefer to talk things out (and I don't mind
> getting flamed, so long as it doesn't get in the way of the work).

I read your messages well.

Linus Torvalds is way more valuable than bcachefs. Please back off.


  reply	other threads:[~2025-08-12  7:17 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
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 [this message]
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=9e81bbfd-1688-46bd-bf38-252fed3b1c82@cock.li \
    --to=asdx52@cock.li \
    --cc=admin@aquinas.su \
    --cc=k.shelekhin@ftml.net \
    --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 \
    /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