Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> writes: > On Thu, Oct 4, 2012 at 12:45 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >> Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx> writes: >> >>> On Thu, Oct 4, 2012 at 1:49 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: >>>> I would recommend against listing any advice.* in the command manual >>>> pages. They are meant to give an advice in cases that are often >>>> confusing to new people and are supposed to advise how to turn it >>>> off in the message. >>> >>> OK. I think I was surprised that some messages were controlled by >>> advice.* but gave no hints about that and I found that out by other >>> means. I'll check all the advice messages. >> >> As far as I can tell, >> >> $ git grep -e 'advice\.' Documentation >> >> shows the list in config.txt and nothing else, and they do talk >> about when they are issued, but the reasoning behind them may not be >> described to a sufficient degree (that is, unless a reader carefully >> thinks things through, s/he may not be able to figure out why). But >> I think what we have there is more or less OK. > > It's about the commands, not the documents. For example I had no idea > I could set advice.statusHints to turn off some advice. "git status" > does not say that those messages can be turned off. OK, the messages are supposed to advise how to turn them off, so we would want some code updates in that case. -- 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