Sitaram Chamarty d8df4a9344 git-config bugfix + backward compat breakage in usage of 'config' ... (1) the backward compat breakage: you can't create empty-valued config keys anymore. That is, you can't do the eqvt of the following shell command using gitolite git config foo.bar "" (2) fixed a bug where this: repo foo config foo.bar = when queried using gitolite git-config -r foo . would return even the empty valued ones, which -- remember! -- are not supposed to exist anymore. Fixing this bug allows situations like this to not show the admin repo in gitweb: repo [a-z].* config gitweb.owner = P-h B repo gitolite-admin config gitweb.owner = ---- background... Somewhere in g3 (well actually in 057506b), we lost the ability to distinguish config foo.bar = "" from config foo.bar = I decided that conflating them is more intuitive for most people, because a survey [1] revealed that no one seemed to want the equivalent of the following shell command: ---- [1] ...of a (small prime greater than 1) number of people on #git		2012-05-04 17:30:22 +05:30
..
ssh-authkeys	logging die and warn messages	2012-04-18 06:23:21 +05:30
update-git-configs	git-config bugfix + backward compat breakage in usage of 'config'	2012-05-04 17:30:22 +05:30
update-git-daemon-access-list	changes to support Solaris default shell	2012-04-18 13:42:50 +05:30
update-gitweb-access-list	changes to support Solaris default shell	2012-04-18 13:42:50 +05:30