git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter van der Does <peter@avirtualhome.com>
To: git@vger.kernel.org
Subject: Re: git config key bug or by design?
Date: Wed, 28 Nov 2012 07:11:47 -0500	[thread overview]
Message-ID: <20121128071147.188a869e@Indy> (raw)
In-Reply-To: <20121128033408.GE27772@sigill.intra.peff.net>

On Tue, 27 Nov 2012 22:34:09 -0500
Jeff King <peff@peff.net> wrote:
> 
> 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").

I am writing a tool, it needs to store branch names in a separate config
file. 

It's clear git doesn't respect those values, hence my question. I
understand how to work around the problem, I would just prefix the key.
I was just wondering if it was by design, which I guess it is as the
parsing of the file will die if the key starts with a non-alpha
character.


-- 
Peter van der Does

GPG key: CB317D6E

IRC: Ganseki on irc.freenode.net
Twitter: @petervanderdoes

  reply	other threads:[~2012-11-28 12:12 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
2012-11-28 12:11   ` Peter van der Does [this message]
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=20121128071147.188a869e@Indy \
    --to=peter@avirtualhome.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 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).