From: Andreas Schwab <schwab@linux-m68k.org>
To: Angelo Borsotti <angelo.borsotti@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git config error message
Date: Sat, 27 Oct 2012 10:25:44 +0200 [thread overview]
Message-ID: <m2bofo9v93.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAB9Jk9AQkSiv=F8NeYs+uspR5f4CeJS5L-hwZUXdq7dts1W5ng@mail.gmail.com> (Angelo Borsotti's message of "Sat, 27 Oct 2012 10:10:04 +0200")
Angelo Borsotti <angelo.borsotti@gmail.com> writes:
> git config --get issues an error message when the specified value
> contains a section that does not exist, but does not issue any message
> when the value contains a key that does not exist while in both cases
> returning a status 1. E.g.
>
> $ git config --get xxx
> error: key does not contain a section: xxx
>
> $ git config --get xxx.yyy
>
> Proposal: to issue an error message also when the key does not exist.
The two cases are different: a key without a section is malformed,
whereas a nonexistent value is usually not an error (use the default
instead).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-10-27 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 8:10 git config error message Angelo Borsotti
2012-10-27 8:25 ` Andreas Schwab [this message]
2012-10-27 8:32 ` Angelo Borsotti
2012-10-27 8:44 ` Andreas Schwab
2012-10-27 8:45 ` Ben Walton
2012-10-27 10:36 ` Angelo Borsotti
2012-10-27 13:14 ` Andreas Schwab
2012-10-27 14:50 ` Angelo Borsotti
2012-10-27 16:12 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2007-11-12 15:35 Jon Smirl
2007-11-12 22:23 ` Alex Riesen
2007-11-12 22:24 ` Johannes Schindelin
2007-11-12 22:26 ` Alex Riesen
2007-11-12 23:09 ` Jakub Narebski
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=m2bofo9v93.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=angelo.borsotti@gmail.com \
--cc=git@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.