From: Theodore Tso <tytso@mit.edu>
To: Girish Shilamkar <girish@clusterfs.com>
Cc: Ext4 Mailing List <linux-ext4@vger.kernel.org>,
Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [Patch 8/13] Config before command line.
Date: Tue, 24 Jul 2007 10:41:57 -0400 [thread overview]
Message-ID: <20070724144157.GD11826@thunk.org> (raw)
In-Reply-To: <1185275102.3789.73.camel@dhcp4.linsyssoft.com>
On Tue, Jul 24, 2007 at 04:35:02PM +0530, Girish Shilamkar wrote:
> The patch changes the order that the config file and command line are parsed so
> that command line has precedence.
#1) Could you please wrap your patch headers at about coulmn 72 or so,
please? Thanks!!
#2) Changing when the config file is parsed doesn't change whether the
command line or the config file has precendence. Parsing the config
file merely sets up an in-memory parse tree so that C code can query
the contents of the config file, e.g.:
profile_get_boolean(ctx->profile, "options",
"defer_check_on_battery", 0, 1,
&defer_check_on_battery);
Simply moving the profile_init() makes no difference. Also, none of
the parameters in /etc/e2fsck.conf overlap with what you can specify
on the command-line, so I'm not even sure what the original author
(Jim Garlick) was even trying to get at.
> It also adds a check to make sure only one -E
> option is passed on the command line as -E option parsing is not cumulative.
Yep, this is reasonable.
- Ted
prev parent reply other threads:[~2007-07-24 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:05 [Patch 8/13] Config before command line Girish Shilamkar
2007-07-24 14:41 ` Theodore Tso [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=20070724144157.GD11826@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=girish@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
/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.