On Sun, Jun 03, 2018 at 06:35:44AM -0400, Robert P. J. Day wrote:
> > > if (for some weird reason) i wanted to define a multi-level
> > > subsection,
> >
> > You can't, there are no multi-level subsections, see above.
>
> no, i *get* that, what i was asking was if i wanted to simulate or
>
Am 03.06.2018 um 11:53 schrieb Robert P. J. Day:
if i wanted to do something this admittedly awkward, would using
periods give me some benefit related to, i don't know, regex matching,
as compared to using a different character? or am i just way
overthinking this? is anyone out there actually
On Sun, 3 Jun 2018, SZEDER Gábor wrote:
>
>
> > 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
> 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
On Fri, 1 Jun 2018, Jeff King wrote:
> On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
... snip ...
> > 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.
On Sat, Jun 02, 2018 at 04:50:57AM -0400, Robert P. J. Day wrote:
> 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
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
On Sat, Jun 02, 2018 at 08:05:22AM +0900, Junio C Hamano wrote:
> > This has been deprecated since 2011. Maybe it's time to finally get rid
> > of it.
>
> Sure, but is it worth the transition noise?
>
> The way we lightly utter the word "deprecated" around here probably
> does not align well
Jeff King writes:
> Syntactically we do allow:
>
> [foo.bar]
> key = true
>
> in the config file, which should equivalent to:
>
> [foo "bar"]
> key = true
>
> This is mentioned later:
>
> There is also a deprecated [section.subsection] syntax. With this
> syntax, the subsection name
On Fri, 1 Jun 2018, Jeff King wrote:
> This is mentioned later:
>
> There is also a deprecated [section.subsection] syntax. With this
> syntax, the subsection name is converted to lower-case and is also
> compared case sensitively. These subsection names follow the same
> restrictions as
On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
> 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.
> -Original Message-
> From: git-ow...@vger.kernel.org On Behalf
> Of Robert P. J. Day
> Sent: June 1, 2018 4:14 PM
> To: Git Mailing list
> Subject: how exactly can git config section names contain periods?
>
>
> more oddities in my travels, this from Doc.../config.txt:
>
> "The
12 matches
Mail list logo
