[PATCH v3 2/4] Documentation: clarify 'complete message'

From: Christian Couder <christian.couder@gmail.com>
Date: Jul 7, 2020, 17:40 UTC
Message-ID: <20200707174049.21714-3-chriscool@tuxfamily.org>
In-Reply-To: <20200707174049.21714-1-chriscool@tuxfamily.org>

In Documentation/git-for-each-ref.txt let's clarify what we mean by "complete message".

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-for-each-ref.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index 2db9779d54..788258c3ad 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -232,8 +232,9 @@ Fields that have name-email-date tuple as its value (`author`,
 `committer`, and `tagger`) can be suffixed with `name`, `email`,
 and `date` to extract the named component.
 
-The complete message of a commit or tag object is `contents`. This
-field can also be used in the following ways:
+The complete message (subject, body, trailers and signature) of a
+commit or tag object is `contents`. This field can also be used in the
+following ways:
 
 contents:subject::
 	The "subject" of the commit or tag message.  It's actually the

-- 
2.27.0.460.g66f3a24dd5