From: Felipe Contreras <felipe.contreras@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 5/8] config: Disallow multiple config file locations.
Date: Sun, 15 Feb 2009 15:35:57 +0200 [thread overview]
Message-ID: <20090215133557.GB13810@annwn> (raw)
In-Reply-To: <94a0d4530902150444t6e4dcd3btda79aaa0efebfe62@mail.gmail.com>
On Sun, Feb 15, 2009 at 02:44:29PM +0200, Felipe Contreras wrote:
> On Sun, Feb 15, 2009 at 2:26 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
> > Hi,
> >
> > On Sun, 15 Feb 2009, Felipe Contreras wrote:
> >
> >> Either --global, --system, or --file should be used, but not any
> >> combination.
> >>
> >> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> >> ---
> >> builtin-config.c | 10 ++++++++++
> >> 1 files changed, 10 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/builtin-config.c b/builtin-config.c
> >> index 83f8b74..e744ad8 100644
> >> --- a/builtin-config.c
> >> +++ b/builtin-config.c
> >> @@ -314,6 +314,16 @@ int cmd_config(int argc, const char **argv, const char *unused_prefix)
> >>
> >> argc = parse_options(argc, argv, builtin_config_options, builtin_config_usage, 0);
> >>
> >> + {
> >> + int config_file_count = use_global_config + use_system_config;
> >> + if (given_config_file)
> >> + config_file_count++;
> >> + if (config_file_count > 1) {
> >> + error("only one config file at a time.");
> >> + usage_with_options(builtin_config_usage, builtin_config_options);
> >> + }
> >> + }
> >
> > Hmm. Is this a convoluted way to write
> >
> > if (use_global_config + use_system_config + !!given_config_file > 1)
> >
> > or am I misunderstanding anything?
>
> Ah, much better. (the !!foo trick is new to me)
Now inlined:
---
builtin-config.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/builtin-config.c b/builtin-config.c
index 30de93e..cdd8a12 100644
--- a/builtin-config.c
+++ b/builtin-config.c
@@ -313,6 +313,11 @@ int cmd_config(int argc, const char **argv, const char *unused_prefix)
argc = parse_options(argc, argv, builtin_config_options, builtin_config_usage, 0);
+ if (use_global_config + use_system_config + !!given_config_file > 1) {
+ error("only one config file at a time.");
+ usage_with_options(builtin_config_usage, builtin_config_options);
+ }
+
if (use_global_config) {
char *home = getenv("HOME");
if (home) {
--
1.6.1.3
--
Felipe Contreras
next prev parent reply other threads:[~2009-02-15 13:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 9:00 [PATCH 1/8] config: Trivial rename in preparation for parseopt Felipe Contreras
2009-02-15 9:00 ` [PATCH 2/8] config: Cleanup config file handling Felipe Contreras
2009-02-15 9:00 ` [PATCH 3/8] config: Use parseopt Felipe Contreras
2009-02-15 9:00 ` [PATCH 4/8] config: Improve variable 'type' handling Felipe Contreras
2009-02-15 9:00 ` [PATCH 5/8] config: Disallow multiple config file locations Felipe Contreras
2009-02-15 9:00 ` [PATCH 6/8] config: Don't allow extra arguments for -e or -l Felipe Contreras
2009-02-15 9:00 ` [PATCH 7/8] config: Don't return negative exit codes Felipe Contreras
2009-02-15 9:01 ` [PATCH 8/8] config: Codestyle cleanups Felipe Contreras
2009-02-15 12:22 ` [PATCH 7/8] config: Don't return negative exit codes Johannes Schindelin
2009-02-15 12:39 ` Felipe Contreras
2009-02-15 13:30 ` Felipe Contreras
2009-02-15 12:26 ` [PATCH 5/8] config: Disallow multiple config file locations Johannes Schindelin
2009-02-15 12:44 ` Felipe Contreras
2009-02-15 13:35 ` Felipe Contreras [this message]
2009-02-15 12:24 ` [PATCH 4/8] config: Improve variable 'type' handling Johannes Schindelin
2009-02-15 12:43 ` Felipe Contreras
2009-02-15 13:34 ` Felipe Contreras
2009-02-15 20:15 ` [PATCH 2/8] config: Cleanup config file handling Jeff King
2009-02-16 1:15 ` Junio C Hamano
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=20090215133557.GB13810@annwn \
--to=felipe.contreras@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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