mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Hill <daniel@gluo.nz>
To: linux-kernel@vger.kernel.org
Cc: Daniel Hill <daniel@gluo.nz>
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc2
Date: Wed,  9 Oct 2024 18:51:50 +1300	[thread overview]
Message-ID: <20241009055217.778948-1-daniel@gluo.nz> (raw)
In-Reply-To: <2nyd5xfm765iklvzjxvn2nx3onhtdntqrnmvlg2panhtdbff7i@evgk5ecmkuoo>

> I'm more than happy to work with people, but that's got to be a
conversation, and one based on mutual respect.

As someone who spent a year and a half working directly with you,
You're full of shit, Linus has spent over 20 years working on
Linux actually collaborating with thousands of people around the
world and then you have the arrogance to think you know how to better
run a collaborative project than him.

You say you care about stability, mutual respect, and making it
easier for your users.

You keep hating on btrfs like an insecure child.

You never afforded any respect to your users, like saying sorry
for your constant temper tantrums on IRC at noobs asking simple
questions.

You put your ego before stability,

Every single version of bcachefs I used for the last 3 years was
a x.x.0 release, I do not recall you ever rebasing to a newer minor
version inbetween major releases. And yet you now cannot empathize
with Linus as you toss 1k lines of code, with missing commit
messages, touching non-bcachefs code moments before the merge window.

You neglect reviewing my branch for a week, with a year old bug
I was working on, you reviewed a different patch, the following
Friday that had been sitting there for 3 months, and was not a
high priority, You accused me of not respecting your time, for
working on the bug fix instead, on the Saturday less than 24
hours later, after wasting my time all week, and the preceding
3 months with the prior patch.

And of course you prioritize your ego over this bug fix and
blocked me when I called you out on this hypocrisy.

That bug fix sits there for another 3 months, being ignored in the
mailing list till I nag you, about it in IRC channel, and ofc you
loved to toss around insults like the man child you are.

You would use any dirty tactic to win arguments, including
personal information I entrusted with you.

Just because you have issues with users having bugs doens't mean you
have the right to create more issues for others.

It's not that hard to setup PPAs for your users. And miss a
merge window every now and then.

I would advise Linus remove bcachefs from the kernel, I have zero
faith he'll change, if there are no consequences for his actions.

> And "upstream rules" has always been a fairly ad-hoc thing, which even
you barely seem able to spell out.

No Kent, Your reading comprehension is just terrible.

No one is on your side Kent, you're the laughing stock to everyone
covering your Drama, no one else needs it "spell out", just you.

You've been a solo dev for over 10 years, and you'll stay a
solo dev for another 10 if you don't harden up, put your big
boy pants on, lay off the weed, and get a therapist.

  parent reply	other threads:[~2024-10-09  5:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-05 18:35 Kent Overstreet
2024-10-05 22:34 ` Linus Torvalds
2024-10-05 22:54   ` Kent Overstreet
2024-10-05 23:15     ` Linus Torvalds
2024-10-05 23:40       ` Kent Overstreet
2024-10-05 23:47         ` Kent Overstreet
2024-10-06  0:14         ` Linus Torvalds
2024-10-06  0:54           ` Kent Overstreet
2024-10-06  4:30             ` Theodore Ts'o
2024-10-06  4:33               ` Kent Overstreet
2024-10-06 19:04                 ` Linus Torvalds
2024-10-06 19:29                   ` Kent Overstreet
2024-10-06 21:31                     ` Alan Huang
2024-10-07 15:01                     ` Jason A. Donenfeld
2024-10-07 19:59                       ` Kent Overstreet
2024-10-07 21:21                         ` Jason A. Donenfeld
2024-10-07 23:33                     ` Jann Horn
2024-10-09  3:51                 ` Theodore Ts'o
2024-10-09  4:17                   ` Kent Overstreet
2024-10-09 17:54                     ` Theodore Ts'o
     [not found]                   ` <CGME20241010085125eucas1p2ad657cb4a5d0bbb9a6a8579406983210@eucas1p2.samsung.com>
2024-10-10  8:51                     ` Daniel Gomez
2024-10-06 11:49             ` Martin Steigerwald
2024-10-06 17:18               ` Kent Overstreet
2024-10-07 15:13                 ` Martin Steigerwald
2024-10-09  5:51             ` Daniel Hill [this message]
2024-10-06  1:20           ` Carl E. Thompson
2024-10-06  1:56             ` Kent Overstreet
2024-10-06  3:06               ` Carl E. Thompson
2024-10-06  3:42                 ` Kent Overstreet
2024-10-07 14:58     ` Josef Bacik
2024-10-07 20:21       ` Kent Overstreet
2024-10-05 22:36 ` pr-tracker-bot

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=20241009055217.778948-1-daniel@gluo.nz \
    --to=daniel@gluo.nz \
    --cc=linux-kernel@vger.kernel.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®