From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Robert P. J. Day'" <rpjday@crashcourse.ca>,
"'Git Mailing list'" <git@vger.kernel.org>
Subject: RE: how exactly can git config section names contain periods?
Date: Fri, 1 Jun 2018 16:50:14 -0400 [thread overview]
Message-ID: <00ce01d3f9ea$270a0d30$751e2790$@nexbridge.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1806011606490.11215@localhost.localdomain>
> -----Original Message-----
> From: git-owner@vger.kernel.org <git-owner@vger.kernel.org> On Behalf
> Of Robert P. J. Day
> Sent: June 1, 2018 4:14 PM
> To: Git Mailing list <git@vger.kernel.org>
> Subject: how exactly can git config section names contain periods?
>
>
> more oddities in my travels, this from Doc.../config.txt:
>
> "The file consists of sections and variables. A section begins with the
name
> of the section in square brackets and continues until the next section
begins.
> Section names are case-insensitive. Only alphanumeric characters, `-` and
`.`
> are allowed in section names.
> ^ ?????
>
> what? how can section names contain periods? reading further,
>
> "Sections can be further divided into subsections. To begin a subsection
put
> its name in double quotes, separated by space from the section name, in
the
> section header, like in the example below:
>
> --------
> [section "subsection"]
>
>
> ok, so how on earth would i use "git config" at the command line to set
a
> config variable with some arbitrary level of subsections? let's try this:
>
> $ git config --global a.b.c.d.e rday
>
> huh ... seemed to work fine, and added this to my ~/.gitconfig:
>
> [a "b.c.d"]
> e = rday
>
> as i see it, the first component is intgerpreted as the section name, the
last
> component is the variable/key(?) name, and everything in between is
> treated as subsection(s), which is not at all obvious from that Doc file,
or from
> "man git-config".
>
> and if a section name can contain periods, how would you specify that at
the
> command line?
I'm with Robert on this. I would have thought that the interpretation should
have been:
["a.b.c.d"]
e = rday
Confused as well,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2018-06-01 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 20:14 how exactly can git config section names contain periods? Robert P. J. Day
2018-06-01 20:50 ` Randall S. Becker [this message]
2018-06-01 21:07 ` Jeff King
2018-06-01 21:55 ` Robert P. J. Day
2018-06-01 23:05 ` Junio C Hamano
2018-06-02 0:02 ` Jeff King
2018-06-02 8:50 ` Robert P. J. Day
2018-06-02 9:26 ` Jeff King
2018-06-03 9:53 ` Robert P. J. Day
2018-06-03 10:35 ` SZEDER Gábor
2018-06-03 10:35 ` Robert P. J. Day
2018-06-04 12:09 ` Jeff King
2018-06-03 10:44 ` Johannes Sixt
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='00ce01d3f9ea$270a0d30$751e2790$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).