Documentation: use lowercase for shallow and deep threading
Even when a sentence is started with 'shallow' or 'deep' use the lowercase version to maintain consistency. Signed-off-by: Stephen Boyd <bebarino@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Stephen Boyd committed
Apr 23, 2009 at 02:37 UTC
fd1ff306b7a02f9412f8ed4881dd239d8a4a709a
2 files changed
+4
-4
Documentation/config.txt
+2
-2
@@ -745,11 +745,11 @@ format.pretty::
745
746
format.thread::
747
The default threading style for 'git-format-patch'. Can be
748
- either a boolean value, `shallow` or `deep`. 'Shallow'
748
+ either a boolean value, `shallow` or `deep`. `shallow`
749
threading makes every mail a reply to the head of the series,
750
where the head is chosen from the cover letter, the
751
`\--in-reply-to`, and the first patch mail, in this order.
752
- 'Deep' threading makes every mail a reply to the previous one.
752
+ `deep` threading makes every mail a reply to the previous one.
753
A true boolean value is the same as `shallow`, and a false
754
value disables threading.
755
Documentation/git-format-patch.txt
+2
-2
@@ -128,9 +128,9 @@ include::diff-options.txt[]
128
the Message-Id header to reference.
129
+
130
The optional <style> argument can be either `shallow` or `deep`.
131
-'Shallow' threading makes every mail a reply to the head of the
131
+'shallow' threading makes every mail a reply to the head of the
132
series, where the head is chosen from the cover letter, the
133
-`\--in-reply-to`, and the first patch mail, in this order. 'Deep'
133
+`\--in-reply-to`, and the first patch mail, in this order. 'deep'
134
threading makes every mail a reply to the previous one. If not
135
specified, defaults to the 'format.thread' configuration, or `shallow`
136
if that is not set.