Re: push.default documented in "man git-push"?
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Oct 5, 2012, 06:34 UTC
- Message-ID
- <CACsJy8BeWuKT_jUyRYf3cKrp7Jx07J2jPEZd96KbWEY+aiX24w@mail.gmail.com>
- In-Reply-To
- <7va9w23i45.fsf@alter.siamese.dyndns.org>
On Thu, Oct 4, 2012 at 12:45 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 21 quoted lines
> Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes: > >> On Thu, Oct 4, 2012 at 1:49 AM, Junio C Hamano <gitster@pobox.com> 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.
-- Duy