From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/4] misc: remove darwin, irix, and freebsd support
Date: Wed, 21 Mar 2018 14:31:38 -0700 [thread overview]
Message-ID: <20180321213138.GA7140@magnolia> (raw)
In-Reply-To: <20180321212617.GX18129@dastard>
On Thu, Mar 22, 2018 at 08:26:17AM +1100, Dave Chinner wrote:
> On Wed, Mar 21, 2018 at 01:59:26PM -0500, Eric Sandeen wrote:
> > On 3/20/18 10:19 PM, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <darrick.wong@oracle.com>
> > >
> > > Remove these ports since they're not actively maintained:
> > >
> > > IRIX support was partially removed last year; the OS itself hasn't had a
> > > release since 2006.
> > >
> > > FreeBSD dropped XFS support in v9.3, which EOLd in January 2017.
> > >
> > > Darwin/OSX has never supported XFS.
> > >
> > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Probably should clean up more than just whole files, see bits & pieces
> > sprinkled throughout:
> >
> > include/builddefs.in
> > include/platform_defs.h.in
> > include/gnukfreebsd.h (?)
>
> So, this makes me wonder. IIRC, that's the header for the debian
> distro on a freebsd kernel. That's a thing, and we package xfsprogs
> in debian. Do they build xfsprogs for that platform, and if they do
> do we care if we break it?
>From the looks of it[1] they (Debian) don't package xfsprogs for
kfreebsd (not even the wheezy release that supposedly had an xfs driver
in the kernle) so I doubt anyone would care.
--D
[1] https://packages.debian.org/search?keywords=xfsprogs
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
next prev parent reply other threads:[~2018-03-21 21:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 3:08 [PATCH 0/4] xfsprogs: more misc fixes Darrick J. Wong
2018-03-20 3:08 ` [PATCH 1/4] xfs_repair: implement custom ifork verifiers Darrick J. Wong
2018-03-20 19:54 ` Eric Sandeen
2018-03-20 21:19 ` Darrick J. Wong
2018-03-20 21:47 ` [PATCH v2 " Darrick J. Wong
2018-03-21 18:37 ` Eric Sandeen
2018-03-22 19:35 ` [PATCH 1.5/4] xfs_repair: use custom ifork verifier in mv_orphanage Eric Sandeen
2018-03-22 19:49 ` Darrick J. Wong
2018-03-20 3:08 ` [PATCH 2/4] libfrog: fs_table_lookup_mount should realpath the argument Darrick J. Wong
2018-03-20 19:55 ` Eric Sandeen
2018-03-20 3:08 ` [PATCH 3/4] xfs_fsr: refactor mountpoint finding to use libfrog paths functions Darrick J. Wong
2018-03-20 23:14 ` Darrick J. Wong
2018-03-21 3:19 ` [PATCH v2 " Darrick J. Wong
2018-03-21 18:49 ` Eric Sandeen
2018-03-20 3:08 ` [PATCH 4/4] mkfs: enable sparse inodes by default Darrick J. Wong
2018-03-20 21:16 ` Eric Sandeen
2018-03-21 3:19 ` [PATCH 5/4] misc: remove darwin, irix, and freebsd support Darrick J. Wong
2018-03-21 18:59 ` Eric Sandeen
2018-03-21 19:01 ` Eric Sandeen
2018-03-21 21:26 ` Dave Chinner
2018-03-21 21:31 ` Darrick J. Wong [this message]
2018-03-21 23:10 ` Dave Chinner
2018-03-21 19:42 ` [PATCH 5.5/4] " Eric Sandeen
2018-03-21 20:13 ` Darrick J. Wong
2018-03-21 3:20 ` [PATCH 6/4] libfrog: absorb platform specific code Darrick J. Wong
2018-03-21 19:52 ` Eric Sandeen
2018-03-26 19:56 ` [PATCH 7/4] xfs_spaceman: remove incorrect linux/fs.h include Darrick J. Wong
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=20180321213138.GA7140@magnolia \
--to=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).