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: <55e623db-ff03-4d33-98d1-1042106e83c6@ftml.net>
Date: Mon, 11 Aug 2025 12:51:11 +0300
From: Konstantin Shelekhin <k.shelekhin@...l.net>
To: kent.overstreet@...ux.dev
Cc: 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

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ