[PATCH] Clarify that a tag can refer to a non-commit object
- From
Robert P. J. Day <rpjday@crashcourse.ca>
- Date
- May 25, 2018, 09:45 UTC
- Message-ID
- <alpine.LFD.2.21.1805250543230.8587@localhost.localdomain>
Reword "man git-tag" to clarify that a tag can refer directly to an arbitrary object, not just a commit object.
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
---
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt index 1d17101ba..87c4288ff 100644 --- a/Documentation/git-tag.txt +++ b/Documentation/git-tag.txt @@ -34,8 +34,8 @@ in the tag message. If `-m <msg>` or `-F <file>` is given and `-a`, `-s`, and `-u <keyid>` are absent, `-a` is implied. -Otherwise just a tag reference for the SHA-1 object name of the commit object is -created (i.e. a lightweight tag). +Otherwise, a tag reference that points directly at the given object +(i.e., a lightweight tag) is created. A GnuPG signed tag object will be created when `-s` or `-u <keyid>` is used. When `-u <keyid>` is not used, the
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================