git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Rune Philosof <rune@philosof.dk>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Complain in the tests about git config not failing with, keys without a section
Date: Mon, 5 Mar 2012 05:37:14 -0500	[thread overview]
Message-ID: <20120305103714.GA30463@sigill.intra.peff.net> (raw)
In-Reply-To: <4F547261.7000506@philosof.dk>

On Mon, Mar 05, 2012 at 08:59:29AM +0100, Rune Philosof wrote:

> On 02-03-2012 19:40, Junio C Hamano wrote:
> >>git is supposed to fail when having a key without a section, but does not.
> >I do not think anybody said it is supposed to fail in this case.
> >
> >the behaviour for a single level name is just "undefined", which is very different from "must fail".
> 
> Quoting from `git help config`:
> This command will fail if:
>  3. no section was provided,

The text you are quoting is not about what is in the config file, but
rather the config name given on the command line (which we would be
trying to look up). And we do correctly complain about that:

  $ git config foo
  error: key does not contain a section: foo

But:

> under SYNTAX
>  Each variable must belong to some section, which means that there
> must be a section header before the first
>        setting of a variable.

Yes, everything is supposed to be in a section.  Historically we have
not complained, but instead just treated it as a single-level variable.
For internal git use this never mattered, as git only looked at
variables with section names. For "git config foo", it also does not
matter, since we will notice the lack of section before even doing a
lookup.

For "git config --list", as you noticed, we include it in the output. I
suspect we should simply omit it as cruft. But we could also issue a
warning, and/or die.

-Peff

  reply	other threads:[~2012-03-05 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 10:57 [PATCH 1/2] Complain in the tests about git config not failing with, keys without a section Rune Schjellerup Philosof
2012-03-02 18:40 ` Junio C Hamano
2012-03-05  7:59   ` Rune Philosof
2012-03-05 10:37     ` Jeff King [this message]
2012-03-05 19:29       ` Junio C Hamano
2012-03-06  8:06         ` Jeff King

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=20120305103714.GA30463@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rune@philosof.dk \
    /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).