From: Jari Aalto <jari.aalto@cante.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms
Date: Mon, 31 Aug 2009 01:00:48 +0300 [thread overview]
Message-ID: <87prad9d2n.fsf@jondo.cante.net> (raw)
In-Reply-To: <7vab1hdppb.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 30 Aug 2009 13:14:24 -0700")
Junio C Hamano <gitster@pobox.com> writes:
>> + operation to a subset of the working tree. See section
>> + ``INTERACTIVE MODE'' for details.
>
> It is not justified with your commit log message, I do not see why you
> have to shout in all CAPS,
There are plenty of examples, that it's standard practise to refer top
level headings, in all caps, from:
POSIX/SusV guides for manual pages: "1.11 Utility Description Defaults"
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap01.html#tag_01_11
Jari
prev parent reply other threads:[~2009-08-30 22:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 17:29 [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms Jari Aalto
2009-08-30 20:14 ` Junio C Hamano
2009-08-30 21:02 ` Jeff King
2009-08-30 21:56 ` Jari Aalto
2009-08-30 22:13 ` Junio C Hamano
2009-08-30 23:06 ` Jari Aalto
2009-08-30 23:20 ` Junio C Hamano
2009-08-31 7:46 ` Jari Aalto
2009-08-31 23:42 ` Junio C Hamano
2009-09-13 6:44 ` [PATCH] Improve --patch option documentation in git-add Jari Aalto
2009-09-13 13:48 ` Mikael Magnusson
2009-09-13 14:09 ` Jari Aalto
2009-09-14 13:13 ` Sean Estabrooks
2009-09-15 5:35 ` [PATCH] Improve --patch option documentation in git-add (updated patch) Jari Aalto
2009-09-15 6:52 ` Nanako Shiraishi
2009-09-15 8:17 ` Jari Aalto
2009-09-15 10:35 ` Nanako Shiraishi
2009-08-30 23:31 ` [PATCH] Documentation/git-add.txt: Explain --patch option in layman terms Junio C Hamano
2009-08-31 7:06 ` Jari Aalto
2009-08-31 7:32 ` Junio C Hamano
2009-08-30 22:00 ` Jari Aalto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prad9d2n.fsf@jondo.cante.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.