All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Tulak <jtulak@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: RFC: removing non-linux platform support from xfsprogs
Date: Fri, 23 Mar 2018 14:07:44 +0100	[thread overview]
Message-ID: <CACj3i70bj7_i0-NRvXhG=9vkA1EKjrE2QDKfB-A2uDeg9ucKsg@mail.gmail.com> (raw)
In-Reply-To: <0204603A-5230-49C1-840B-CDB9053FB72D@sandeen.net>

On Fri, Mar 23, 2018 at 1:59 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>
>
>> On Mar 23, 2018, at 4:10 AM, Jan Tulak <jtulak@redhat.com> wrote:
>>
>> On Thu, Mar 22, 2018 at 8:50 PM, Darrick J. Wong
>> <darrick.wong@oracle.com> wrote:
>>> On Sat, May 27, 2017 at 11:17:30AM -0500, Eric Sandeen wrote:
>>>>
>>>>
>>>>> On 5/27/17 2:41 AM, Jan Tulak wrote:
>>>>>> On Fri, May 26, 2017 at 11:47 PM, Eric Sandeen <sandeen@sandeen.net> wrote:
>>>>>> There's a bunch of mucking about to try to build xfsprogs on non-linux
>>>>>> platforms.  Is anyone using that, or care about it?  If not, I propose
>>>>>> removing it all in a cruft-reducing effort.
>>>>>>
>>>>>> If I'm missing some good reason for it to be there, please educate me,
>>>>>> and I'll leave it alone.
>>>>>>
>>>>>> In particular, Jan - I know you did a lot of this work - do you still
>>>>>> use it?
>>>>>>
>>>>>
>>>>> I used the macos stuff at the beginning to get into the code with
>>>>> little risk of breaking anything. Until it is possible to mount xfs in
>>>>> the other systems, xfsprogs is useless there... So, I'm ok with the
>>>>> removal of macos code. I don't know how it is with the other systems,
>>>>> though.
>>>>
>>>> Ok, thanks - honestly if you still use it, that's fine.  But if you're
>>>> not ... and nobody else is ... let's nuke it.  ;)
>>>
>>> Ten months and nobody else has said anything, let's nuke non-linux
>>> support.
>>>
>>
>> Sure. Are you working on it, or would you appreciate if someone took
>> care of it? :-)
>>
>
> Patches are already on the list :)
>

Ah, sorry, I didn't see that one. Thanks.

Jan

      reply	other threads:[~2018-03-23 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 21:47 RFC: removing non-linux platform support from xfsprogs Eric Sandeen
2017-05-27  7:41 ` Jan Tulak
2017-05-27 16:17   ` Eric Sandeen
2018-03-22 19:50     ` Darrick J. Wong
2018-03-23  9:10       ` Jan Tulak
2018-03-23 12:59         ` Eric Sandeen
2018-03-23 13:07           ` Jan Tulak [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='CACj3i70bj7_i0-NRvXhG=9vkA1EKjrE2QDKfB-A2uDeg9ucKsg@mail.gmail.com' \
    --to=jtulak@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.