git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ping Yin" <pkufranky@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Should 'git config' support key with dot such as 'a.b'
Date: Tue, 18 Mar 2008 08:40:46 +0800	[thread overview]
Message-ID: <46dff0320803171740of822d02medc5911e0d056eb4@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0803141138340.24600@racer.site>

On Fri, Mar 14, 2008 at 6:39 PM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
>
>  On Fri, 14 Mar 2008, Ping Yin wrote:
>
>  > I find it is so annoying to write submodule definition as follows
>  > (yeah, only url, without path)
>  >
>  > ------------------------------
>  > [submodule 'crawler']
>  >     url = url1
>  > [submodule 'search']
>  >     url = url2
>  > ------------------------------
>  >
>  > I think the following form is more simple
>  > ---------------------------------
>  > [submodule]
>  >      crawler.url = url1
>  >      search.url = url2
>  > ---------------------------------
>  >
>  > So, could we support such simpler form?
>
>  I don't like it at all.  Historically, we had much stricter rules on the
>  variable names than the second part of the section names.
>
>  Also, your suggestion would make things even more confusing than beginners
>  already complain Git is.
>

Beginners will not edit config file directly. If they do, they can
follow the usaual syntax. So beginners don't have to know the new
syntax.

But for advanced users, the config file can be edited freely with more
free syntax. With current syntax, 'submodule'  will be repeated tons
of times when having tons of submoudles. Why not make life much easier
for advanced users in such case?



-- 
Ping Yin

  reply	other threads:[~2008-03-18  0:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14  8:24 Should 'git config' support key with dot such as 'a.b' Ping Yin
2008-03-14 10:39 ` Johannes Schindelin
2008-03-18  0:40   ` Ping Yin [this message]
2008-03-18  0:42     ` Junio C Hamano
2008-03-17  1:00 ` Xavier Maillard
2008-03-17  8:48   ` Frank Lichtenheld
2008-03-17  9:03     ` Frank Lichtenheld

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=46dff0320803171740of822d02medc5911e0d056eb4@mail.gmail.com \
    --to=pkufranky@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /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).