John Keeping <john@xxxxxxxxxxxxx> writes: > Since commit 00b347d (git-config: do not complain about duplicate > entries, 2012-10-23), "git config --get" does not exit with an error if > there are multiple values for the specified key but instead returns the > last value. Update the documentation to reflect this. > > Signed-off-by: John Keeping <john@xxxxxxxxxxxxx> > --- > Documentation/git-config.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt > index 19a7be0..fbad05e 100644 > --- a/Documentation/git-config.txt > +++ b/Documentation/git-config.txt > @@ -82,7 +82,7 @@ OPTIONS > --get:: > Get the value for a given key (optionally filtered by a regex > matching the value). Returns error code 1 if the key was not > - found and error code 2 if multiple key values were found. > + found and the last value if multiple key values were found. > > --get-all:: > Like get, but does not fail if the number of values for the key Thanks. I wondered if we should explain the significance of "last" a bit more (like "this results in the value from the most specific configuration file to be used, the ones in $GIT_DIR/config overriding what is in $HOME/.gitconfig"), but I do not have a strong opinion either way. Let's queue this for 'maint' for now. -- 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