[PATCH 3/8] Documentation: use lowercase for shallow and deep threading
- From
Stephen Boyd <bebarino@gmail.com>
- Date
- Apr 23, 2009, 09:37 UTC
- Message-ID
- <1240479482-31366-4-git-send-email-bebarino@gmail.com>
- In-Reply-To
- <1240479482-31366-3-git-send-email-bebarino@gmail.com>
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> --- Documentation/config.txt | 4 ++-- Documentation/git-format-patch.txt | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt index a8b68e2..cabac97 100644 --- a/Documentation/config.txt +++ b/Documentation/config.txt @@ -745,11 +745,11 @@ format.pretty:: format.thread:: The default threading style for 'git-format-patch'. Can be - either a boolean value, `shallow` or `deep`. 'Shallow' + either a boolean value, `shallow` or `deep`. `shallow` threading makes every mail a reply to the head of the series, where the head is chosen from the cover letter, the `\--in-reply-to`, and the first patch mail, in this order. - 'Deep' threading makes every mail a reply to the previous one. + `deep` threading makes every mail a reply to the previous one. A true boolean value is the same as `shallow`, and a false value disables threading. diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index 5eddca9..4a43c64 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -128,9 +128,9 @@ include::diff-options.txt[] the Message-Id header to reference. + The optional <style> argument can be either `shallow` or `deep`. -'Shallow' threading makes every mail a reply to the head of the +'shallow' threading makes every mail a reply to the head of the series, where the head is chosen from the cover letter, the -`\--in-reply-to`, and the first patch mail, in this order. 'Deep' +`\--in-reply-to`, and the first patch mail, in this order. 'deep' threading makes every mail a reply to the previous one. If not specified, defaults to the 'format.thread' configuration, or `shallow` if that is not set.
-- 1.6.2.3