{"thread":{"id":"34153","subject":"[PATCH 0/2] Add missing calls to git_config()","startedAt":"2013-06-15T20:28:23Z","lastAt":"2013-06-15T20:28:23Z","messageCount":1,"participants":["Ramsay Jones"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"220961","messageId":"51BCCE67.9010105@ramsay1.demon.co.uk","threadId":"34153","inReplyTo":null,"subject":"[PATCH 0/2] Add missing calls to git_config()","fromName":"Ramsay Jones","fromEmail":"ramsay@ramsay1.demon.co.uk","sentAt":"2013-06-15T20:28:23Z","receivedAt":"2013-06-15T20:28:23Z","isPatch":true,"sender":{"key":"ramsay@ramsayjones.plus.com","avatar":"https://avatars.githubusercontent.com/u/33702710?v=4"},"body":"\nHi Junio,\n\nI recently had need to use the '-c' option to git in order to\nset some config variables from the command line; specifically\nwith 'git show-ref' and 'git pack-refs'. I haven't looked to\nsee if any other commands need similar attention, but:\n\n    $ git grep 'cmd_.*(int argc' -- builtin | wc -l\n    109\n    $ git grep 'git_config(' -- builtin | wc -l\n    80\n    $\n\n... maybe. ;-)\n\n[I did think about separating the command line processing from\nthe config file processing; maybe some commands could accept\nconfig settings from the command line, but do not need/want\nthe regular config file processing? *dunno*.]\n\nATB,\nRamsay Jones\n\nRamsay Jones (2):\n  show-ref.c: Add missing call to git_config()\n  pack-refs.c: Add missing call to git_config()\n\n builtin/pack-refs.c | 3 +++\n builtin/show-ref.c  | 2 ++\n 2 files changed, 5 insertions(+)\n\n-- \n1.8.3\n"}]}