summaryrefslogtreecommitdiff
path: root/Documentation/git-mktag.txt
diff options
context:
space:
mode:
authorJonathan Maw <jonathan.maw@codethink.co.uk>2013-09-27 17:19:40 +0000
committerJonathan Maw <jonathan.maw@codethink.co.uk>2013-09-27 17:19:40 +0000
commit7bf8e474d15414eda8520ba5258511d845ca6061 (patch)
tree417d6cfc8946fce8e2f87fdf3ec964036abd495c /Documentation/git-mktag.txt
parent45d74c4b0fe38218b4569a90da7102cf48d616c2 (diff)
parente230c568c4b9a991e3175e5f65171a566fd8e39c (diff)
downloadgit-7bf8e474d15414eda8520ba5258511d845ca6061.tar.gz
Merge tag 'v1.8.4' into baserock/morph
Git 1.8.4
Diffstat (limited to 'Documentation/git-mktag.txt')
-rw-r--r--Documentation/git-mktag.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-mktag.txt b/Documentation/git-mktag.txt
index 65e167a5c5..3ca158b05e 100644
--- a/Documentation/git-mktag.txt
+++ b/Documentation/git-mktag.txt
@@ -28,9 +28,9 @@ A tag signature file has a very simple fixed format: four lines of
tagger <tagger>
followed by some 'optional' free-form message (some tags created
-by older git may not have `tagger` line). The message, when
+by older Git may not have `tagger` line). The message, when
exists, is separated by a blank line from the header. The
-message part may contain a signature that git itself doesn't
+message part may contain a signature that Git itself doesn't
care about, but that can be verified with gpg.
GIT