On Fri, Jun 22, 2007 at 01:56:00AM +0200, Jakub Narebski wrote: > 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? > > I don't know, but at least two scripts use --get-regexp, namely > git-remote and git-submodule. So we would have to be careful about > changing that. > > > I would be enough to add the following to your patch: Yeah, I found this a but ugly though so I left it out of the first patch in case someone had a better idea. Will include that in the second version (which will also include documentation). > By the way, I have tried to use git-config --null to redo config > file parsing in gitweb, so one git-config call would be needed for > all the config. I have noticed that --bool option description does > not describe the observed behavior fully. For example it returns > 'true' not only for '1', but for any integer != 0, including 0xdeadbeef. Yeah, the description of --bool is very incomplete. Note that empty values are false, and keys without values are true. I think this all are valid choices, but they are indeed not documented. Gruesse. -- Frank Lichtenheld <frank@xxxxxxxxxxxxxx> www: http://www.djpig.de/ - 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
