git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jeff King <peff@peff.net>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: how exactly can git config section names contain periods?
Date: Sat, 2 Jun 2018 04:50:57 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1806020448030.24235@localhost.localdomain> (raw)
In-Reply-To: <20180601210731.GA20974@sigill.intra.peff.net>

On Fri, 1 Jun 2018, Jeff King wrote:

> On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
>
> >   $ 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".
>
> Yep, your understanding is correct.

  just to be precise regarding terminology, in my example above, is
"b.c.d" a single subsection, or does it refer to three subsections?
i'm guessing it refers to a single subsection, which is fine with me,
as long as it's very clearly explained that way in the docs.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  parent reply	other threads:[~2018-06-02  8:53 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
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 [this message]
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=alpine.LFD.2.21.1806020448030.24235@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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).