From: milki <milki@rescomp.berkeley.edu>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-config: case insensitivity for subsections
Date: Thu, 25 Aug 2011 14:57:57 -0700 [thread overview]
Message-ID: <20110825215757.GA94231@hal.rescomp.berkeley.edu> (raw)
In-Reply-To: <20110825205849.GA10384@sigill.intra.peff.net>
On 16:58 Thu 25 Aug , Jeff King wrote:
> Is there a reason that you can't use the canonical version in your "git
> config" invocation? Or was it simply confusing that it didn't work? I'd
> much prefer to document this limitation in git-config(1) than change the
> code.
This was simply surprising as I was trying to figure out what exactly
case sensitivity meant and how it affacted sections. This definitely
clears this up for me. I'm actually working on a config parser because I
don't think I've seen a complete implementation besides git-config in a
different language.
next prev parent reply other threads:[~2011-08-25 21:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 6:35 git-config: case insensitivity for subsections milki
2011-08-25 20:58 ` Jeff King
2011-08-25 21:32 ` Junio C Hamano
2011-08-25 21:39 ` Jeff King
2011-08-25 21:57 ` milki [this message]
2011-08-29 0:50 ` Alex Vandiver
2011-08-29 5:42 ` milki
2011-08-29 15:58 ` Jeff King
2011-08-29 16:47 ` Alex Vandiver
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=20110825215757.GA94231@hal.rescomp.berkeley.edu \
--to=milki@rescomp.berkeley.edu \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).