From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Eric Sandeen <sandeen@sandeen.net>, Dave Chinner <david@fromorbit.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] mkfs: remove notion of config "type"
Date: Thu, 14 Jun 2018 18:19:17 +0200 [thread overview]
Message-ID: <20180614161917.GA7508@wotan.suse.de> (raw)
In-Reply-To: <8c2a5a07-5d47-48a1-1593-e93eb0fb883a@sandeen.net>
On Wed, Jun 13, 2018 at 02:37:01PM -0500, Eric Sandeen wrote:
> -static inline const char *default_type_str(enum default_params_type type)
> -{
> - switch (type) {
> - case DEFAULTS_BUILTIN:
> - return _("package built-in definitions");
> - case DEFAULTS_CONFIG:
> - return _("package default config file");
> - case DEFAULTS_CLI_CONFIG:
> - return _("CLI supplied file");
> - }
> - return _("Unkown\n");
> -}
>
> - printf(_("Default configuration sourced from %s\n"),
> - default_type_str(dft.type));
The above is really the reason to the type stuff, and it was also why
I added it, as otherwise we had to allocate a string for the old way of
supplying that data. So really this is about the *source*, the type enum
stuff is just a way to implement it without dealing with complexities
on the string.
So regardless of the type, the question is we are OK to loose the source
of where the config file info came from. I think it is important information
to get, but since it is not not information kept on the actual filesystem it is
information lost, and so really only useful for deployment time. But since
we are already printing the actual file used... it may suffice, and I do
agree I this does simplify things more.
Chinner had added that print line, I just tried to keep it around, if he's cool
with the removal of the source stuff now, then sure.
Luis
next prev parent reply other threads:[~2018-06-14 16:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 19:33 [PATCH 0/2] mkfs: 2 more fixes Eric Sandeen
2018-06-13 19:34 ` [PATCH 1/2] mkfs: initialize return value of parse_config_stream to success Eric Sandeen
2018-06-14 8:48 ` Carlos Maiolino
2018-06-14 16:20 ` Luis R. Rodriguez
2018-06-14 16:41 ` Darrick J. Wong
2018-06-13 19:37 ` [PATCH 2/2] mkfs: remove notion of config "type" Eric Sandeen
2018-06-14 9:46 ` Carlos Maiolino
2018-06-14 16:19 ` Luis R. Rodriguez [this message]
2018-06-14 16:40 ` Eric Sandeen
2018-06-14 16:41 ` Darrick J. Wong
2018-06-14 23:42 ` Dave Chinner
[not found] ` <CAB=NE6V7JmsPpkCB1zp0CuY5YTJvMonG7UJPjScKYVJZLWb3xg@mail.gmail.com>
2018-06-15 2:33 ` Dave Chinner
2018-06-15 2:45 ` Eric Sandeen
2018-06-16 0:17 ` Dave Chinner
2018-06-16 0:55 ` Eric Sandeen
2018-06-16 2:44 ` Dave Chinner
2018-06-16 4:35 ` cfg file versioning (was: [PATCH 2/2] mkfs: remove notion of config "type") Eric Sandeen
2018-06-14 15:43 ` [PATCH 3/2] mkfs: manpage fixups in config file section Eric Sandeen
2018-06-14 16:43 ` Darrick J. Wong
2018-06-14 16:20 ` [PATCH 4/2] mkfs: add -c option to the --help screen Darrick J. Wong
2018-06-14 16:34 ` Eric Sandeen
2018-06-14 16:49 ` Luis R. Rodriguez
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=20180614161917.GA7508@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=david@fromorbit.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 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).