From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 1/5] mkfs: Don't emit default config message yet
Date: Thu, 7 Dec 2017 20:21:53 -0800 [thread overview]
Message-ID: <20171208042153.GI19219@magnolia> (raw)
In-Reply-To: <62f67117-150d-e456-d9dd-3a19938cb03a@sandeen.net>
On Thu, Dec 07, 2017 at 10:13:15PM -0600, Eric Sandeen wrote:
> Until we have more than one possible source of configuration,
> there is no need to emit the only possibility and clutter
> the output. We can decide how it should all look when we
> get more than one source.
>
> Apply some i18n to the config description, though.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Looks ok, I guess,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
(I wonder why Dave put the printf in there, but I'll let him answer that.)
> ---
>
> mkfs/xfs_mkfs.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index e38810f..0f7dd92 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -3845,7 +3845,7 @@ main(
>
> /* build time defaults */
> struct mkfs_default_params dft = {
> - .source = "package build definitions",
> + .source = _("package build definitions"),
> .sectorsize = XFS_MIN_SECTORSIZE,
> .blocksize = 1 << XFS_DFL_BLOCKSIZE_LOG,
> .sb_feat = {
> @@ -3881,10 +3881,12 @@ main(
> * defaults. If a file exists in <package location>, read in the new
> * default values and overwrite them in the &dft structure. This way the
> * new defaults will apply before we parse the CLI, and the CLI will
> - * still be able to override them. Emit a message to indicate where the
> - * defaults being used came from.
> + * still be able to override them. When more than one source is
> + * implemented, emit a message to indicate where the defaults being
> + * used came from.
> + *
> + * printf(_("Default configuration sourced from %s\n"), dft.source);
> */
> - printf(_("Default configuration sourced from %s\n"), dft.source);
>
> /* copy new defaults into CLI parsing structure */
> memcpy(&cli.sb_feat, &dft.sb_feat, sizeof(cli.sb_feat));
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-08 4:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 4:11 [PATCH 0/5] mkfs: minor tidyups Eric Sandeen
2017-12-08 4:13 ` [PATCH 1/5] mkfs: Don't emit default config message yet Eric Sandeen
2017-12-08 4:21 ` Darrick J. Wong [this message]
2017-12-08 4:54 ` Dave Chinner
2017-12-08 13:37 ` Eric Sandeen
2017-12-08 4:13 ` [PATCH 2/5] mkfs: remove unused m_uuid in sb_feat_args Eric Sandeen
2017-12-08 4:22 ` Darrick J. Wong
2017-12-08 4:15 ` [PATCH 3/5] mkfs: invert project id width boolean name Eric Sandeen
2017-12-08 4:18 ` Darrick J. Wong
2017-12-08 4:17 ` [PATCH 4/5] mkfs: document sb_feat_args members Eric Sandeen
2017-12-08 4:27 ` Darrick J. Wong
2017-12-08 4:59 ` Dave Chinner
2017-12-08 4:18 ` [PATCH 5/5] mkfs: remove use-once default macros Eric Sandeen
2017-12-08 4:27 ` Darrick J. Wong
2017-12-08 5:01 ` [PATCH 0/5] mkfs: minor tidyups Dave Chinner
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=20171208042153.GI19219@magnolia \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox