English â–¾
Localized versions of git-mktag manual
Topics â–¾
Email
Version 2.0.5
â–¾
git-mktag last updated in 2.43.0
Changes in the git-mktag manual
Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.43.1 → 2.47.0 no changes
-
2.43.0
11/20/23
- 2.42.1 → 2.42.3 no changes
-
2.42.0
08/21/23
- 2.32.1 → 2.41.2 no changes
-
2.32.0
06/06/21
- 2.31.1 → 2.31.8 no changes
-
2.31.0
03/15/21
- 2.7.6 → 2.30.9 no changes
-
2.6.7
05/05/17
- 2.1.4 → 2.5.6 no changes
-
2.0.5
12/17/14
DESCRIPTION
Reads a tag contents on standard input and creates a tag object that can also be used to sign other objects.
The output is the new tag’s <object> identifier.
Tag Format
A tag signature file has a very simple fixed format: four lines of
object <sha1> type <typename> tag <tagname> tagger <tagger>
followed by some optional free-form message (some tags created
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
care about, but that can be verified with gpg.
GIT
Part of the git[1] suite
