Re: push.default documented in "man git-push"?

On Thu, Oct 11, 2012 at 9:18 PM, Matthieu Moy
[off-list ref] wrote:

For example, it makes the output of git status look like:

# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#   Set advice.statusHints to false to turn off this message
#
#       modified:   foo.txt
#
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#   Set advice.statusHints to false to turn off this message
#
#       modified:   foo.txt
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#   Set advice.statusHints to false to turn off this message
#
#       bar.txt

And two more lines on my output:

 no changes added to commit (use "git add" and/or "git commit -a")
 Set advice.statusHints to false to turn off this message

I think it's going really too far in verbosity, the actual information
is hidden by the advices.

We could make it only one extra line in this case by prepending "hint:
" before the advice and say "you could turn the hints off by setting
advice.statusHints" at the end. Not applicable in general though.

quoted

(which is good, more motivation to turn advice off).

I disagree. Having advices turned on doesn't harm anyone. I don't
remember anyone complaining about the verbosity of Git's advices. I've
seen *many* more people complaining about the user-unfriendliness of
Git.

"git status" is actually quite verbose, but the advice only plays a
part of it. So, not an actual complaint from me about the advice
alone.

quoted

-     "  git checkout -b new_branch_name\n\n";
+     "  git checkout -b new_branch_name\n"
+     "Set either advice.detachedHead to false to turn off this message\n\n"

            ^^^^^^

Wrong cut-and paste from "... either XXX or YYY ..."? (repeated several
times below).

Cut&Paste mistake.
-- 
Duy