lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <rabpjlpydnsnlkrgqmolvgg5tyo2kk5v45evwdt6ffetsqynfy@dt2r3cxio5my>
Date: Tue, 12 Aug 2025 03:04:19 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: asdx <asdx52@...k.li>
Cc: Konstantin Shelekhin <k.shelekhin@...l.net>, admin@...inas.su, 
	linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	list-bcachefs@...lthompson.net, malte.schroeder@...ip.de, torvalds@...ux-foundation.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17

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).

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ