From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dave Chinner <david@fromorbit.com>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfsprogs v4.15.0-rc1 released
Date: Fri, 23 Feb 2018 01:56:42 +0000 [thread overview]
Message-ID: <20180223015642.GA27199@wotan.suse.de> (raw)
In-Reply-To: <b5f653da-d56d-550f-645c-36da93ba7441@sandeen.net>
On Thu, Feb 22, 2018 at 02:49:27PM -0600, Eric Sandeen wrote:
> On 2/20/18 3:02 PM, Dave Chinner wrote:
> > If this is really a huge problem for distros, then wasn't this what
> > someone wanted mkfs config files for?
>
> Suse folk seem to like that approach, yes. But while the config
> file facilitates that sort of distro approach, it isn't really
> a hard requirement, I'd think - patching is always an option
> in the end.
Clearly. Its still a nice sensible feature to address any defaults,
and now that I see chinner/mkfs-refactor is merged I'll go work
off of that and post patches again soon.
Luis
next prev parent reply other threads:[~2018-02-23 1:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 20:29 [ANNOUNCE] xfsprogs v4.15.0-rc1 released Eric Sandeen
2018-02-20 0:36 ` Christoph Hellwig
2018-02-20 15:09 ` Eric Sandeen
2018-02-20 16:33 ` Darrick J. Wong
2018-02-20 21:02 ` Dave Chinner
2018-02-22 20:49 ` Eric Sandeen
2018-02-22 23:44 ` Dave Chinner
2018-02-23 18:33 ` Darrick J. Wong
2018-02-23 22:14 ` Dave Chinner
2018-02-23 1:56 ` Luis R. Rodriguez [this message]
2018-02-23 1:59 ` 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=20180223015642.GA27199@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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 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).