David Glasser <glasser@xxxxxxxxxxxxxxxx> writes: > Signed-off-by: David Glasser <glasser@xxxxxxxxxxxxxxxx> > --- > Documentation/git-config.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt > index f163113..83f86b9 100644 > --- a/Documentation/git-config.txt > +++ b/Documentation/git-config.txt > @@ -263,6 +263,9 @@ The files are read in the order given above, with > last value found taking No need to resend but the above context line somehow got line-wrapped. > precedence over values read earlier. When multiple values are taken then all > values of a key from all files will be used. > > +You may override individual configuration parameters when running any git > +command by using the `-c` option. See linkgit:git[1] for details. > + This is not a new (as linkgit:git[1] also has it) but "override" is a white lie, and may invite nitpickers. The -c var=val given from the "git" command line is merely tacked at the end of the search order, so it would "override" when the variable is used as a single-valued variable, but when it is used as multi-valued one, it does not. That might be something we want to fix up further in later patches; the change we see in this patch is good regardless. Thanks. > All writing options will per default write to the repository specific > configuration file. Note that this also affects options like `--replace-all` > and `--unset`. *'git config' will only ever change one file at a time*. -- 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