From: "Christopher Snowhill" <chris@kode54.net>
To: "Carl E. Thompson" <list-bcachefs@carlthompson.net>,
"Kent Overstreet" <kent.overstreet@linux.dev>
Cc: "linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>
Subject: Re: Another bcachefs version downgrade bug
Date: Fri, 18 Oct 2024 01:17:06 -0700 [thread overview]
Message-ID: <D4YS7TRT48VG.3LCDBSZGAVBSZ@kode54.net> (raw)
In-Reply-To: <504302838.942.1729183773058@mail.carlthompson.net>
On Thu Oct 17, 2024 at 9:49 AM PDT, Carl E. Thompson wrote:
>
>
> > On 2024-10-17 3:13 AM PDT Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> > ...
>
> > Carl, I'm happy to fix bugs that you find, but the attitude and the
> > unnecessary advice - that I don't enjoy.
>
> Seriously, Kent? **You're** talking to **me** about attitude?
>
> **You're** giving **me** passive-aggressive attitude about how I'm reporting a bug when using a kernel which is only 4 months old. And how about that crack about about how I should have just done an fsck when you knew (should have known) that a fsck doesn't fix the problem? I don't doubt that in your mind those are subtle insults that would fly right over my head and I wouldn't notice but I might suggest that other people aren't quite the idiots you seem to always assume we are.
>
> I'm trying to **help** you, Kent. And that includes the reminder about how long it takes to put mostly-done software into a usable state. That's not attitude, that's just reality.
>
> Carl
FYI, 6.9 was first released in May, and is already EOL now. In fact, so
is 6.10, at 6.10.14. There are no LTS kernels with bcachefs support yet
at this point. All further development is going into 6.12 now, with bug
fixes being backported into 6.11.
The only distributions still shipping 6.9 or 6.10 are backporting things
themselves. Actually, last I recall, there's at least one distribution
that decided to slap 6.8 into an LTS as well. I guess big distributions
just *love* doing their own backport work.
- Christopher
next prev parent reply other threads:[~2024-10-18 8:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 4:51 Another bcachefs version downgrade bug Carl E. Thompson
2024-10-17 0:09 ` Kent Overstreet
2024-10-17 8:29 ` Carl E. Thompson
2024-10-17 8:39 ` Kent Overstreet
2024-10-17 9:15 ` Carl E. Thompson
2024-10-17 9:30 ` Kent Overstreet
2024-10-17 9:45 ` Carl E. Thompson
2024-10-17 10:13 ` Kent Overstreet
2024-10-17 16:49 ` Carl E. Thompson
2024-10-18 8:17 ` Christopher Snowhill [this message]
2024-10-18 17:37 ` Carl E. Thompson
2024-10-18 19:12 ` Kent Overstreet
2024-10-19 0:15 ` Carl E. Thompson
2024-10-19 8:13 ` Malte Schröder
2024-10-19 8:31 ` Martin Steigerwald
2024-10-19 9:29 ` Carl E. Thompson
2024-10-20 9:29 ` Kent Overstreet
2024-10-19 20:18 ` Jani Partanen
2024-10-20 8:04 ` Malte Schröder
2024-10-21 3:49 ` Jani Partanen
2024-10-20 16:59 ` Kent Overstreet
2024-10-21 0:34 ` Carl E. Thompson
2024-10-21 1:15 ` Kent Overstreet
2024-10-21 7:43 ` Mounting multiple versions/snapshots/images at the same time (was: Re: Another bcachefs version downgrade bug) Martin Steigerwald
2024-10-21 20:15 ` Carl E. Thompson
2024-10-21 7:26 ` Another bcachefs version downgrade bug 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=D4YS7TRT48VG.3LCDBSZGAVBSZ@kode54.net \
--to=chris@kode54.net \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=list-bcachefs@carlthompson.net \
/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