From: Jeff King <peff@peff.net>
To: Peter van der Does <peter@avirtualhome.com>
Cc: git@vger.kernel.org
Subject: Re: git config key bug or by design?
Date: Tue, 27 Nov 2012 22:34:09 -0500 [thread overview]
Message-ID: <20121128033408.GE27772@sigill.intra.peff.net> (raw)
In-Reply-To: <20121127221446.7f2fbf71@Indy>
On Tue, Nov 27, 2012 at 10:14:46PM -0500, Peter van der Does wrote:
> I noticed today I can't create a key starting with a number.
>
> The source code[1] confirms this, but is this a bug or is it by design?
I don't recall ever discussing it. But what is it that you want to store
in a key starting with a number? Git does not respect any such config
values[1].
Are you writing a new tool that will store its config alongside git's?
Even if the behavior is loosened, you would probably want to avoid
starting your config keys with numbers, as older git versions would be
around for a while and would choke on it.
-Peff
[1] You can still store arbitrary bytes in the subsection name (e.g.,
"foo.123.bar").
next prev parent reply other threads:[~2012-11-28 3:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 3:14 git config key bug or by design? Peter van der Does
2012-11-28 3:34 ` Jeff King [this message]
2012-11-28 12:11 ` Peter van der Does
2012-11-28 20:21 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2012-11-28 2:57 Peter van der Does
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=20121128033408.GE27772@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=peter@avirtualhome.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;
as well as URLs for NNTP newsgroup(s).