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

Re: [PATCH] push: Provide situational hints for non-fast-forward errors

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Mar 14, 2012, 13:00 UTC
Message-ID
<vpqobrzgww9.fsf@bauges.imag.fr>
In-Reply-To
<20120314121434.GB28595@in.waw.pl>
Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> writes:
> I think that having three different config keys for the three
> different advices makes sense, because the advices will be displayed
> at different times.

I don't think it really makes sense to be such fine-grained. We already have 6 different advices, so an advance user who do not want them need to set these 6 variables. I think we want to keep this number relatively low.

The advice messages do not point explicitely to the way to disable them, so users who know how to set advice.* are users who know a little about configuration files, and who read the docs. Instead of having too fine-grained configuration variables, we can have a better doc, explaining shortly the 3 possible cases under advice.nonfastforward in config.txt. The user who disable the advice can read the doc (I usually think that "users don't read documentation" is a better assumption, but since the user knows about the name of the variable, it is OK here).

Also, if I read correctly the patch, the old variable is left in the doc and in advice.{c,h}, but is no longer used. This means old-timers who have set it will see the message poping-up again after they upgrade, which I think is inconveinient for them.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Zbigniew Jędrzejewski-SzmekNext: Zbigniew Jędrzejewski-Szmek
Message 4 of 28 in “push: Provide situational hints for non-fast-forward errors”
  1. push: Provide situational hints for non-fast-forward errorsChristopher Tiwald, Mar 13, 2012
  2. Junio C HamanoMar 14, 2012
  3. Zbigniew Jędrzejewski-SzmekMar 14, 2012
  4. Matthieu MoyMar 14, 2012
  5. Zbigniew Jędrzejewski-SzmekMar 14, 2012
  6. Christopher TiwaldMar 14, 2012
  7. Clemens BuchacherMar 15, 2012
  8. Junio C HamanoMar 15, 2012
  9. Matthieu MoyMar 16, 2012
  10. Christopher TiwaldMar 14, 2012
  11. Christopher TiwaldMar 14, 2012
  12. Matthieu MoyMar 14, 2012
  13. Christopher TiwaldMar 14, 2012
  14. Junio C HamanoMar 14, 2012
  15. Junio C HamanoMar 16, 2012
  16. Clemens BuchacherMar 16, 2012
  17. Junio C HamanoMar 16, 2012
  18. Christopher TiwaldMar 16, 2012
  19. Junio C HamanoMar 16, 2012
  20. Junio C HamanoMar 16, 2012
  21. Clemens BuchacherMar 16, 2012
  22. Junio C HamanoMar 16, 2012
  23. Clemens BuchacherMar 16, 2012
  24. Junio C HamanoMar 16, 2012
  25. push: Provide situational hints for non-fast-forward errorsZbigniew Jędrzejewski-Szmek, Mar 17, 2012
  26. Christopher TiwaldMar 17, 2012
  27. Zbigniew Jędrzejewski-SzmekMar 17, 2012
  28. Junio C HamanoMar 19, 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.