From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.12-rc2
Date: Sat, 5 Oct 2024 15:34:56 -0700 [thread overview]
Message-ID: <CAHk-=wjit-1ETRxCBrQAw49AUcE5scEM5O++M=793bDWnQktmw@mail.gmail.com> (raw)
In-Reply-To: <cphtxla2se4gavql3re5xju7mqxld4rp6q4wbqephb6by5ibfa@5myddcaxerpb>
On Sat, 5 Oct 2024 at 11:35, Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> Several more filesystems repaired, thank you to the users who have been
> providing testing. The snapshots + unlinked fixes on top of this are
> posted here:
I'm getting really fed up here Kent.
These have commit times from last night. Which makes me wonder how
much testing they got.
And before you start whining - again - about how you are fixing bugs,
let me remind you about the build failures you had on big-endian
machines because your patches had gotten ZERO testing outside your
tree.
That was just last week, and I'm getting the strong feeling that
absolutely nothing was learnt from the experience.
I have pulled this, but I searched for a couple of the commit messages
on the lists, and found *nothing* (ok, I found your pull request,
which obviously mentioned the first line of the commit messages).
I'm seriously thinking about just stopping pulling from you, because I
simply don't see you improving on your model. If you want to have an
experimental tree, you can damn well have one outside the mainline
kernel. I've told you before, and nothing seems to really make you
understand.
I was hoping and expecting that bcachefs being mainlined would
actually help development. It has not. You're still basically the
only developer, there's no real sign that that will change, and you
seem to feel like sending me untested stuff that nobody else has ever
seen the day before the next rc release is just fine.
You're a smart person. I feel like I've given you enough hints. Why
don't you sit back and think about it, and let's make it clear: you
have exactly two choices here:
(a) play better with others
(b) take your toy and go home
Those are the choices.
Linus
next prev parent reply other threads:[~2024-10-05 22:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 18:35 [GIT PULL] bcachefs fixes for 6.12-rc2 Kent Overstreet
2024-10-05 22:34 ` Linus Torvalds [this message]
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-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='CAHk-=wjit-1ETRxCBrQAw49AUcE5scEM5O++M=793bDWnQktmw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).