From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"Jeff King" <peff@peff.net>,
"Git Mailing list" <git@vger.kernel.org>
Subject: Re: how exactly can git config section names contain periods?
Date: Sun, 3 Jun 2018 12:35:10 +0200 [thread overview]
Message-ID: <20180603103510.21020-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1806030547070.5332@localhost.localdomain>
> On Fri, 1 Jun 2018, Jeff King wrote:
>
> > On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
> > > 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:
> >
> > You don't. There are only three levels: section, (optional)
> > subsection, and key. If there is a subsection, it consists of
> > _everything_ between the two outer periods.
<snip>
> if (for some weird reason) i wanted to define a multi-level
> subsection,
You can't, there are no multi-level subsections, see above.
next prev parent reply other threads:[~2018-06-03 10:35 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
2018-06-02 9:26 ` Jeff King
2018-06-03 9:53 ` Robert P. J. Day
2018-06-03 10:35 ` SZEDER Gábor [this message]
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=20180603103510.21020-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.