linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aquinas Admin <admin@aquinas.su>
To: kent.overstreet@linux.dev, Konstantin Shelekhin <k.shelekhin@ftml.net>
Cc: 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: Mon, 11 Aug 2025 23:45:09 +0700	[thread overview]
Message-ID: <13820530.uLZWGnKmhe@woolf> (raw)
In-Reply-To: <55e623db-ff03-4d33-98d1-1042106e83c6@ftml.net>

В письме от понедельник, 11 августа 2025 г. 16:51:11 Красноярск, стандартное 
время пользователь Konstantin Shelekhin написал:
> > 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.

Come on? It's been around for 30 years because it's financially beneficial for 
some players. Should we forget about the letters and insults that flew around 
before 2018? The Code of Conduct wasn't introduced just like that. Well, 
that's just a small remark, in general. The fact is, there are no objections 
to the technical quality of Bcachefs. The objections are exclusively about 
Kent's personality and how he conducts his affairs. Maybe someone experienced 
in resolving such issues and handling personnel conflicts could suggest a 
solution? Analyze the situation and offer methods for resolution? Especially 
since the problem is far from being solely about Kent. I suggest that instead 
of threats, hasty conclusions, and quick decisions, we turn to professionals 
with the right expertise, who are surely present in the Linux Foundation. It 
will take time, but it will help everyone become better. I hope everyone 
understands that the right solution shouldn't be dictated by someone's 
feelings or grudges—regardless of who's involved.



  parent reply	other threads:[~2025-08-11 16:45 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
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 [this message]
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=13820530.uLZWGnKmhe@woolf \
    --to=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;
as well as URLs for NNTP newsgroup(s).