linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] mkfs: remove notion of config "type"
Date: Fri, 15 Jun 2018 09:42:39 +1000	[thread overview]
Message-ID: <20180614234239.GO10363@dastard> (raw)
In-Reply-To: <20180614164121.GC6825@magnolia>

On Thu, Jun 14, 2018 at 09:41:21AM -0700, Darrick J. Wong wrote:
> On Wed, Jun 13, 2018 at 02:37:01PM -0500, Eric Sandeen wrote:
> > @@ -3796,19 +3795,18 @@ _("respecification of configuration not allowed\n"));
> >  		ret = parse_defaults_file(fd, &dft, config_file);
> >  		if (ret) {
> >  			fprintf(stderr,
> > -_("Error parsing %s config file: %s : %s\n"),
> > -				default_type_str(dft.type),
> > +_("Error parsing config file: %s : %s\n"),
> >  				config_file, strerror(errno));
> >  			free(config_file);
> >  			close(fd);
> >  			exit(1);
> >  		}
> > +		printf(_("Configuration file used for defaults: %s\n"),
> 
> _("EXPERIMENTAL configuration file used for defaults: %s\n")

I don't see a reason for this to be experimental - we're not
screwing with on-disk formats and there's no potential for data
corruption or loss, so why do we need to mark this as "don't use
this because it might screw up your data"?  I'd much prefer we spend
the time now to get it right before before shipping it...

Which then makes me ask: why don't we have a config file version
identifier in the config file?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2018-06-14 23:45 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
2018-06-14 16:40     ` Eric Sandeen
2018-06-14 16:41   ` Darrick J. Wong
2018-06-14 23:42     ` Dave Chinner [this message]
     [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=20180614234239.GO10363@dastard \
    --to=david@fromorbit.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 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).