linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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: Sun, 6 Oct 2024 00:30:02 -0400	[thread overview]
Message-ID: <20241006043002.GE158527@mit.edu> (raw)
In-Reply-To: <2nyd5xfm765iklvzjxvn2nx3onhtdntqrnmvlg2panhtdbff7i@evgk5ecmkuoo>

On Sat, Oct 05, 2024 at 08:54:32PM -0400, Kent Overstreet wrote:
> But I also have to remind you that I'm one of the few people who's
> actually been pushing for more and better automated testing (I now have
> infrastructure for the communty that anyone can use, just ask me for an
> account) - and that's been another solo effort because so few people are
> even interested, so the fact that this even came up grates on me. This
> is a problem with a technical solution, and instead we're all just
> arguing.

Um, hello?  All of the file system developers have our own automated
testing, and my system, {kvm,gce,android}-xfstests[1][[2] and Luis's
kdevops[3] are both availble for others to use.  We've done quite a
lot in terms of doumentations and making it easier for others to use.
(And that's not incluing the personal test runners used by folks like
Josef, Cristoph, Dave, and Darrick.)

[1] https://thunk.org/gce-xfstest
[2] https://github.com/tytso/xfstests-bld
[3] https://github.com/linux-kdevops/kdevops

That's why we're not particularly interested in yours --- my system
has been in active use since 2011, and it's been well-tuned for me and
others to use.  (For example, Leah has been using it for XFS stable
backports, and it's also used for testing Google's Data Center
kernels, and GCE's Cloud Optimized OS.)

You may believe that yours is better than anyone else's, but with
respect, I disagree, at least for my own workflow and use case.  And
if you look at the number of contributors in both Luis and my xfstests
runners[2][3], I suspect you'll find that we have far more
contributors in our git repo than your solo effort....

					- Ted

  reply	other threads:[~2024-10-06  4:30 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
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 [this message]
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=20241006043002.GE158527@mit.edu \
    --to=tytso@mit.edu \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).