Re: [PATCH/RFC] config: Add --null/-z option for null-delimted output
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jun 19, 2007, 00:55 UTC
- Message-ID
- <Pine.LNX.4.64.0706190151160.4059@racer.site>
- In-Reply-To
- <11821227322913-git-send-email-frank@lichtenheld.de>
Hi,
On Mon, 18 Jun 2007, Frank Lichtenheld wrote:
> Note the FIXME. Does anyone remember the reason why --get-regexp > and --list use different output format?
AFAIK --list was meant as a replacement to git-var --list. Thus, it had to behave exactly the same.
As for the FIXME: If you have a config like this:
[core] Some = where over the = core.rainbow
git-config -z would output something like this:
core.some\0where\0core.over\0core.the\0core.rainbow\0
Right?
As you can see, it is quite hard for a parser to find out what is key, and what is value. That FIXME is _exactly_ about this dilemma.
IIRC I stated once that -z should output a value of "true" for these cases, since they only make sense as booleans. But AFAIR nothing conclusive came out of that thread.
Ciao, Dscho