2005-05-10 21:32:30 +00:00
|
|
|
git-mktag(1)
|
|
|
|
============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
git-mktag - Creates a tag object
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2011-07-02 02:38:26 +00:00
|
|
|
[verse]
|
2008-06-30 06:09:04 +00:00
|
|
|
'git mktag' < signature_file
|
2005-05-10 21:32:30 +00:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2005-05-10 21:32:38 +00:00
|
|
|
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
|
|
|
|
----------
|
2007-06-10 23:00:36 +00:00
|
|
|
A tag signature file has a very simple fixed format: four lines of
|
2005-05-10 21:32:38 +00:00
|
|
|
|
|
|
|
object <sha1>
|
|
|
|
type <typename>
|
|
|
|
tag <tagname>
|
2007-06-10 23:00:36 +00:00
|
|
|
tagger <tagger>
|
2005-05-10 21:32:38 +00:00
|
|
|
|
2007-06-10 23:00:36 +00:00
|
|
|
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.
|
2005-05-10 21:32:30 +00:00
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 07:07:32 +00:00
|
|
|
Part of the linkgit:git[1] suite
|