{"thread":{"id":"43915","subject":"[PATCH] doc: mention `git -c` in git-config(1)","startedAt":"2016-08-23T17:33:48Z","lastAt":"2016-09-12T02:19:57Z","messageCount":5,"participants":["David Glasser","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"299969","messageId":"CAN7QDo+S21T=1zjBEM7rq3epzvVx7GhmTZ5+sgV0BPvNYhvvUg@mail.gmail.com","threadId":"43915","inReplyTo":null,"subject":"[PATCH] doc: mention `git -c` in git-config(1)","fromName":"David Glasser","fromEmail":"glasser@davidglasser.net","sentAt":"2016-08-23T17:33:21Z","receivedAt":"2016-08-23T17:33:48Z","isPatch":true,"sender":{"key":"glasser@davidglasser.net","avatar":"https://avatars.githubusercontent.com/u/16724?v=4"},"body":"Signed-off-by: David Glasser \n---\n Documentation/git-config.txt | 3 +++\n 1 file changed, 3 insertions(+)\n\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex f163113..83f86b9 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -263,6 +263,9 @@ The files are read in the order given above, with\nlast value found taking\n precedence over values read earlier. When multiple values are taken then all\n values of a key from all files will be used.\n\n+You may override individual configuration parameters when running any git\n+command by using the `-c` option. See linkgit:git[1] for details.\n+\n All writing options will per default write to the repository specific\n configuration file. Note that this also affects options like `--replace-all`\n and `--unset`. *'git config' will only ever change one file at a time*.\n-- \n2.8.1\n"},{"id":"299977","messageId":"xmqqd1kzwegi.fsf@gitster.mtv.corp.google.com","threadId":"43915","inReplyTo":"CAN7QDo+S21T=1zjBEM7rq3epzvVx7GhmTZ5+sgV0BPvNYhvvUg@mail.gmail.com","subject":"Re: [PATCH] doc: mention `git -c` in git-config(1)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-08-23T18:02:53Z","receivedAt":"2016-08-23T18:09:56Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Glasser writes:\n\n> Signed-off-by: David Glasser \n> ---\n> Documentation/git-config.txt | 3 +++\n> 1 file changed, 3 insertions(+)\n>\n> diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\n> index f163113..83f86b9 100644\n> --- a/Documentation/git-config.txt\n> +++ b/Documentation/git-config.txt\n> @@ -263,6 +263,9 @@ The files are read in the order given above, with\n> last value found taking\n\nNo need to resend but the above context line somehow got line-wrapped.\n\n> precedence over values read earlier. When multiple values are taken then all\n> values of a key from all files will be used.\n>\n> +You may override individual configuration parameters when running any git\n> +command by using the `-c` option. See linkgit:git[1] for details.\n> +\n\nThis is not a new (as linkgit:git[1] also has it) but \"override\" is\na white lie, and may invite nitpickers. The -c var=val given from\nthe \"git\" command line is merely tacked at the end of the search\norder, so it would \"override\" when the variable is used as a\nsingle-valued variable, but when it is used as multi-valued one, it\ndoes not.\n\nThat might be something we want to fix up further in later patches;\nthe change we see in this patch is good regardless.\n\nThanks.\n\n> All writing options will per default write to the repository specific\n> configuration file. Note that this also affects options like `--replace-all`\n> and `--unset`. *'git config' will only ever change one file at a time*.\n"},{"id":"301682","messageId":"CAN7QDoJOzVvCzM80v=jP7RTB0od4exFLMZGkvPx9Uz6Lkm16Tg@mail.gmail.com","threadId":"43915","inReplyTo":"xmqqd1kzwegi.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH] doc: mention `git -c` in git-config(1)","fromName":"David Glasser","fromEmail":"glasser@davidglasser.net","sentAt":"2016-09-12T00:33:48Z","receivedAt":"2016-09-12T00:34:15Z","isPatch":true,"sender":{"key":"glasser@davidglasser.net","avatar":"https://avatars.githubusercontent.com/u/16724?v=4"},"body":"On Tue, Aug 23, 2016 at 11:02 AM, Junio C Hamano wrote:\n> David Glasser writes:\n>\n> That might be something we want to fix up further in later patches;\n> the change we see in this patch is good regardless.\n\n\nPerhaps I am looking at the wrong branch, but I'm not sure that this\ngot merged? Is there something I should do to move this along?\n\n--dave\n\n-- \nglasser@davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/\n"},{"id":"301687","messageId":"xmqqeg4p6fxb.fsf@gitster.mtv.corp.google.com","threadId":"43915","inReplyTo":"CAN7QDoJOzVvCzM80v=jP7RTB0od4exFLMZGkvPx9Uz6Lkm16Tg@mail.gmail.com","subject":"Re: [PATCH] doc: mention `git -c` in git-config(1)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-09-12T01:54:40Z","receivedAt":"2016-09-12T01:55:15Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Glasser writes:\n\n> On Tue, Aug 23, 2016 at 11:02 AM, Junio C Hamano wrote:\n>> David Glasser writes:\n>>\n>> That might be something we want to fix up further in later patches;\n>> the change we see in this patch is good regardless.\n>\n>\n> Perhaps I am looking at the wrong branch, but I'm not sure that this\n> got merged? Is there something I should do to move this along?\n\nAre you asking about \"might be something we want to fix up further\",\nwhich I do not think anybody did (and you certainly didn't)?\n\nThe patch that was commented on in that exchange should be part of\nv2.10.0 already.\n\n$ git blame -s -L264,269 v2.10.0 Documentation/git-config.txt\n7da9800f 264) values of a key from all files will be used.\n7da9800f 265) \nae1f7094 266) You may override individual configuration parameters when running any git\nae1f7094 267) command by using the `-c` option. See linkgit:git[1] for details.\nae1f7094 268) \n17014090 269) All writing options will per default write to the repository specific\n\n$ git show ae1f7094\ncommit ae1f7094f7a68fcff3d07358d83f5f483f0c300c\nAuthor: David Glasser \nDate: Tue Aug 23 10:33:21 2016 -0700\n\n doc: mention `git -c` in git-config(1)\n \n Signed-off-by: David Glasser \n Signed-off-by: Junio C Hamano \n\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex 6843114..636b3eb 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -263,6 +263,9 @@ The files are read in the order given above, with last value found taking\n precedence over values read earlier. When multiple values are taken then all\n values of a key from all files will be used.\n \n+You may override individual configuration parameters when running any git\n+command by using the `-c` option. See linkgit:git[1] for details.\n+\n All writing options will per default write to the repository specific\n configuration file. Note that this also affects options like '--replace-all'\n and '--unset'. *'git config' will only ever change one file at a time*.\n"},{"id":"301689","messageId":"CAN7QDo+9QN6QVqqeZh9_0h0=MtZik_HLQLnCOFabrAYFgHcANA@mail.gmail.com","threadId":"43915","inReplyTo":"xmqqeg4p6fxb.fsf@gitster.mtv.corp.google.com","subject":"Re: [PATCH] doc: mention `git -c` in git-config(1)","fromName":"David Glasser","fromEmail":"glasser@davidglasser.net","sentAt":"2016-09-12T02:19:30Z","receivedAt":"2016-09-12T02:19:57Z","isPatch":true,"sender":{"key":"glasser@davidglasser.net","avatar":"https://avatars.githubusercontent.com/u/16724?v=4"},"body":"On Sun, Sep 11, 2016 at 6:54 PM, Junio C Hamano wrote:\n> The patch that was commented on in that exchange should be part of\n> v2.10.0 already.\n\nMy mistake: I was accidentally searching for the paragraph I added in\nconfig.txt instead of git-config.txt. Thanks and sorry for wasting\nyour time!\n\n--dave\n\n-- \nglasser@davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/\n"}]}