'\" t
.\" Title: git-mktag
.\" Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 06/01/2011
.\" Manual: Git Manual
.\" Source: Git 1.7.5.4
.\" Language: English
.\"
.TH "GIT\-MKTAG" "1" "06/01/2011" "Git 1\&.7\&.5\&.4" "Git Manual"
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
git-mktag \- Creates a tag object
.SH "SYNOPSIS"
.sp
\fIgit mktag\fR < signature_file
.SH "DESCRIPTION"
.sp
Reads a tag contents on standard input and creates a tag object that can also be used to sign other objects\&.
.sp
The output is the new tag\(cqs <object> identifier\&.
.SH "TAG FORMAT"
.sp
A tag signature file has a very simple fixed format: four lines of
.sp
.if n \{\
.RS 4
.\}
.nf
object <sha1>
type <typename>
tag <tagname>
tagger <tagger>
.fi
.if n \{\
.RE
.\}
.sp
followed by some \fIoptional\fR 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\(cqt care about, but that can be verified with gpg\&.
.SH "GIT"
.sp
Part of the \fBgit\fR(1) suite