git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 11, 2012, 16:17 UTC
Message-ID
<7vehl57zkh.fsf@alter.siamese.dyndns.org>
In-Reply-To
<vpqhaq13xdq.fsf@grenoble-inp.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 13 quoted lines
> Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
>
>> On Fri, Oct 05, 2012 at 01:03:28PM -0700, Junio C Hamano wrote:
>>
>>> OK, the messages are supposed to advise how to turn them off, so we
>>> would want some code updates in that case.
>>
>> Something like this? It turns out none of the advice messages says
>> anything about advice.*.
>
> Personally, I'm fine with the current situation. Advanced users can read
> the documentation, and for others, the messages are usually more helpful
> than annoying.
OK, you convinced me.
Show 14 quoted lines
> 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.
>
> I'm fine with very verbose (and scary) messages when the user did
> something wrong (for example, the advice.implicitIdentity is something
> you should never see if you configured Git properly before commiting).
> But the user should not feel blamed for using the default configuration
> of advice messages. The tripple repetition in "git status" shown above
> really sounds like "hey, dumb user, why did you not set
> advice.statusHints already", and is doubly scary for newbies, because
> they are not told how to set the variable, nor what a config variable is
> to Git.

Let's let the list of advice.* messages in Documentation/config.txt do their job.

Nguyen, thanks for taking a look. I do agree the extra "here is how to rob helpful hints from yourself before you learn them" seems to do more harm than good.

Previous: Nguyen Thai Ngoc DuyNext: Peter Krefting
Message 34 of 35 in “push.default documented in "man git-push"?”
  1. David GlasserOct 2, 2012
  2. Ramkumar RamachandraOct 2, 2012
  3. David GlasserOct 2, 2012
  4. Ramkumar RamachandraOct 2, 2012
  5. Matthieu MoyOct 2, 2012
  6. Ramkumar RamachandraOct 2, 2012
  7. Junio C HamanoOct 2, 2012
  8. Matthieu MoyOct 2, 2012
  9. Junio C HamanoOct 2, 2012
  10. David GlasserOct 2, 2012
  11. Junio C HamanoOct 2, 2012
  12. Matthieu MoyOct 3, 2012
  13. Ramkumar RamachandraOct 3, 2012
  14. Nguyen Thai Ngoc DuyOct 3, 2012
  15. Ramkumar RamachandraOct 3, 2012
  16. Nguyen Thai Ngoc DuyOct 3, 2012
  17. Ramkumar RamachandraOct 3, 2012
  18. Nguyen Thai Ngoc DuyOct 3, 2012
  19. Junio C HamanoOct 3, 2012
  20. Jeff KingOct 3, 2012
  21. Junio C HamanoOct 8, 2012
  22. Ramkumar RamachandraOct 7, 2012
  23. Junio C HamanoOct 7, 2012
  24. Ramkumar RamachandraOct 8, 2012
  25. Nguyen Thai Ngoc DuyOct 8, 2012
  26. Junio C HamanoOct 3, 2012
  27. Nguyen Thai Ngoc DuyOct 4, 2012
  28. Junio C HamanoOct 4, 2012
  29. Nguyen Thai Ngoc DuyOct 5, 2012
  30. Junio C HamanoOct 5, 2012
  31. Nguyen Thai Ngoc DuyOct 11, 2012
  32. Matthieu MoyOct 11, 2012
  33. Nguyen Thai Ngoc DuyOct 11, 2012
  34. Junio C HamanoOct 11, 2012
  35. Peter KreftingOct 3, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.