Re: [RFC] Git config file reader in Perl (WIP)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote:
> Hi,
> 
> On Tue, 16 Jan 2007, Junio C Hamano wrote:
> 
> > "Nikolai Weibull" <now@xxxxxxxx> writes:
> > 
> > > If we're going down this slippery slope, why not just give up and add
> > > a --xml switch instead?  Readable by all...
> > 
> > Perhaps all except humans.
> > 
> > At least YAML, please...
> 
> I am _strongly_ opposed to all that rubbish. _If_ we want to use 
> repo-config to preformat the config variables, we should either
> 
> 1) just use "git repo-config -l" and STFU, or
> 2) introduce something like "--dump" which Eric implemented.
> 
> Everything else is just _complicating_ matters, and for _what_? _Nothing_ 
> at all. If we use repo-config for that task, it should cater for parsing 
> by _script languages_, not _users_.
> 
> I work with XML everyday. It has its uses. But this here problem is _not_ 
> one of them. How silly would that be: we parse an easy-to-read format, 
> munge the easy-to-handle internal data format into another "easy-to-read" 
> format which is then parsed by a script language into an easy-to-handle 
> internal data format? No. NO.

I agree with these statements.  I actually had YAML in my code
originally, but ripped it out because it would be another round of
parsing for any language using a YAML parser.

I like YAML, but no, this isn't the place for it IMHO.

-- 
Eric Wong
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]