From: Carlos Maiolino <cmaiolino@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: [RFC] xfsprogs: remove irix, darwin, freebsd support
Date: Thu, 22 Mar 2018 21:21:02 +0100 [thread overview]
Message-ID: <20180322202102.wpff347scdmfpv62@odin.usersys.redhat.com> (raw)
In-Reply-To: <17870b11-8567-7938-e510-dbc22fd107f6@sandeen.net>
On Thu, Mar 22, 2018 at 02:49:42PM -0500, Eric Sandeen wrote:
> On 3/20/18 7:14 PM, Darrick J. Wong wrote:
> > Hi all,
> >
> > This is a metapatch proposing that we drop all the non-Linux xfsprogs
> > ports.
> >
> > Irix hasn't had a release since August 2006.
> >
> > OSX doesn't support XFS and (afaict) never has.
> >
> > FreeBSD EOL'd v9.3 (which was the last one to support XFS) in January
> > 2017.
> >
> > So, can we git rm {include,libxfs}/{irix,darwin,freebsd}.[ch] ?
>
> I sent out the same query in May 2017,
> "RFC: removing non-linux platform support from xfsprogs"
>
> and nobody really chimed in to keep any of it. I'm happy to nuke it,
> and if someone comes back with a tail of woe, we can always put it back
> in place if it's deemed wise.
>
+1, FreeBSD never meant to actually have a 'fully supported' XFS port anyway,
and nobody was interested in updating it to comply with their VFS changes
between 9 and 10, so they just decided to drop it. And Irix is EOL, so I believe
it's safe to remove it.
--
Carlos
prev parent reply other threads:[~2018-03-22 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 0:14 [RFC] xfsprogs: remove irix, darwin, freebsd support Darrick J. Wong
2018-03-22 19:49 ` Eric Sandeen
2018-03-22 20:21 ` Carlos Maiolino [this message]
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=20180322202102.wpff347scdmfpv62@odin.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.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;
as well as URLs for NNTP newsgroup(s).