Re: Should 'git config' support key with dot such as 'a.b'

From: Frank Lichtenheld <frank@lichtenheld.de>
Date: Mar 17, 2008, 08:48 UTC
Message-ID: <20080317084815.GC10103@mail-vs.djpig.de>
In-Reply-To: <200803170100.m2H103CF020765@localhost.localdomain>

On Mon, Mar 17, 2008 at 02:00:03AM +0100, Xavier Maillard wrote:

Show 18 quoted lines

>    I think the following form is more simple
>    ---------------------------------
>    [submodule]
> 	crawler.url = url1
> 	search.url = url2
>    ---------------------------------
> 
>    So, could we support such simpler form?
> 
> Dunno if my vote will count but I really don't like your
> proposition. I find clearer with the current notation. What's
> more it forces people to be more rigorous when touching their
> configuration file.
> 
> git config is really simple to use and there should not be
> difficult for anybody (even new git users) to set up git using
> this helper tool. We should not recommend beginners to manually
> edit their .git/config file when git-config could be used.

git config hasn't exactly a excellent track-record for dealing with all the possibilities the config syntax allows. Adding yet another possibility will not make it any more reliable.

Also your argument that people should git-config anyway instead of editing by hand kinda contradicts the need for a new format, since it would change anything for the git-config interface, only for people editing the file by hand...

At the end of the day I don't think the benefits justify the effort.

Gruesse,

-- 
Frank Lichtenheld <frank@lichtenheld.de>
www: http://www.djpig.de/