summaryrefslogtreecommitdiffstats
path: root/git-mktag.html
diff options
context:
space:
mode:
Diffstat (limited to 'git-mktag.html')
-rw-r--r--git-mktag.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/git-mktag.html b/git-mktag.html
index 835253a7b..037c05c81 100644
--- a/git-mktag.html
+++ b/git-mktag.html
@@ -757,7 +757,7 @@ git-mktag(1) Manual Page
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<div class="paragraph"><p>Reads a tag contents on standard input and creates a tag object. The
+<div class="paragraph"><p>Reads a tag&#8217;s contents on standard input and creates a tag object. The
output is the new tag&#8217;s &lt;object&gt; identifier.</p></div>
<div class="paragraph"><p>This command is mostly equivalent to <a href="git-hash-object.html">git-hash-object(1)</a>
invoked with <code>-t tag -w --stdin</code>. I.e. both of these will create and
@@ -769,7 +769,7 @@ git hash-object -t tag -w --stdin &lt;my-tag</code></pre>
</div></div>
<div class="paragraph"><p>The difference is that mktag will die before writing the tag if the
tag doesn&#8217;t pass a <a href="git-fsck.html">git-fsck(1)</a> check.</p></div>
-<div class="paragraph"><p>The "fsck" check done mktag is stricter than what <a href="git-fsck.html">git-fsck(1)</a>
+<div class="paragraph"><p>The "fsck" check done by mktag is stricter than what <a href="git-fsck.html">git-fsck(1)</a>
would run by default in that all <code>fsck.&lt;msg-id&gt;</code> messages are promoted
from warnings to errors (so e.g. a missing "tagger" line is an error).</p></div>
<div class="paragraph"><p>Extra headers in the object are also an error under mktag, but ignored
@@ -811,7 +811,7 @@ tag &lt;tagname&gt;
tagger &lt;tagger&gt;</code></pre>
</div></div>
<div class="paragraph"><p>followed by some <em>optional</em> free-form message (some tags created
-by older Git may not have <code>tagger</code> line). The message, when it
+by older Git may not have a <code>tagger</code> line). The message, when it
exists, is separated by a blank line from the header. The
message part may contain a signature that Git itself doesn&#8217;t
care about, but that can be verified with gpg.</p></div>
@@ -828,7 +828,7 @@ care about, but that can be verified with gpg.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2023-06-23 13:24:09 PDT
+ 2023-10-23 14:43:46 PDT
</div>
</div>
</body>