From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 0/5] fstests: remove old SGI QE scripts
Date: Thu, 6 Mar 2025 14:59:55 -0800 [thread overview]
Message-ID: <20250306225955.GF2803740@frogsfrogsfrogs> (raw)
In-Reply-To: <20250306213921.3769440-1-david@fromorbit.com>
On Fri, Mar 07, 2025 at 08:34:45AM +1100, Dave Chinner wrote:
> Hi folks,
>
> The scripts this patchset removes are historical relics. They
> haven't been maintained, in many cases they don't work, and in a
> couple fo cases they are reliant on test machines that SGI
> decomissioned almost two decades ago.
>
> There is no point in trying to maintain these scripts, but they
> still create dependencies on common fstests code that is now getting
> in the way of making changes to fstests infrastructure.
>
> Hence we should simply remove them and get rid of all the technical
> debt they contain with them.
The whole set looks good to me -- I've definitely never needed, used, or
noticed the old SGI scripts.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> -Dave.
>
>
next prev parent reply other threads:[~2025-03-06 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:34 [PATCH 0/5] fstests: remove old SGI QE scripts Dave Chinner
2025-03-06 21:34 ` [PATCH 1/5] fstests: remove setup script Dave Chinner
2025-03-06 21:34 ` [PATCH 2/5] fstests: remove old soak script Dave Chinner
2025-03-06 21:34 ` [PATCH 3/5] fstests: remove crash script Dave Chinner
2025-03-06 21:34 ` [PATCH 4/5] fstests: remove tools/auto-qa Dave Chinner
2025-03-06 21:34 ` [PATCH 5/5] fstests: remove old tools from tools directory Dave Chinner
2025-03-06 22:59 ` Darrick J. Wong [this message]
2025-03-07 4:04 ` [PATCH 0/5] fstests: remove old SGI QE scripts David Disseldorp
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=20250306225955.GF2803740@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=fstests@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