From: Eryu Guan <eguan@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/6] xfstests: remove most IRIX-specific code
Date: Thu, 1 Jun 2017 15:29:02 +0800 [thread overview]
Message-ID: <20170601072902.GY23805@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170601032904.GA1083@zzz>
On Wed, May 31, 2017 at 08:29:04PM -0700, Eric Biggers wrote:
> On Thu, Jun 01, 2017 at 11:12:35AM +0800, Eryu Guan wrote:
> > On Wed, May 31, 2017 at 03:36:49PM -0700, Eric Biggers wrote:
> > > From: Eric Biggers <ebiggers@google.com>
> > >
> > > For some time xfstests has de facto not supported IRIX anymore. The
> > > final release of IRIX was over 10 years ago and it seems no one has
> > > been running the latest xfstests releases on any IRIX system, as at
> > > the very least xfstests now assumes the existence of some util-linux
> > > binaries. There are probably other examples of this bitrot too.
> > >
> > > Therefore, this patchset simplifies things removing IRIX support from
> > > the xfstests tests, build system, and documentation.
> > >
> > > It focuses on making larger, more obvious cleanups. Of course,
> > > there's more to do if people want to spend more time going through
> > > some of the more intricate details, especially XFS-specific details.
> > > But this should be a good start.
> >
> > Thanks a lot for doing this!! I didn't see patch #2 and #3 hit the list
> > (too big for the list?). Do you have a public git repo that I can pull
> > from?
> >
>
> Ick, I guess the size limit must be 100K. I've pushed the series out to
> repository https://github.com/ebiggers/xfstests, branch "remove_irix_support".
>
> Note that the two biggest patches can be more easily reviewed with
> 'git diff -D', since that abbreviates the file deletions.
Thanks!
I also cc'ed linux-xfs list for review, as IRIX support is mainly for
XFS.
Eryu
next parent reply other threads:[~2017-06-01 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170531223655.130613-1-ebiggers3@gmail.com>
[not found] ` <20170601031235.GV23805@eguan.usersys.redhat.com>
[not found] ` <20170601032904.GA1083@zzz>
2017-06-01 7:29 ` Eryu Guan [this message]
2017-06-01 15:33 ` [PATCH 0/6] xfstests: remove most IRIX-specific code Darrick J. Wong
2017-06-02 1:25 ` Eric Biggers
2017-06-02 2:54 ` Eryu Guan
2017-06-02 3:34 ` Eryu Guan
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=20170601072902.GY23805@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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).