]>
Commit | Line | Data |
---|---|---|
2cf565c5 DG |
1 | git-mktag(1) |
2 | ============ | |
2cf565c5 DG |
3 | |
4 | NAME | |
5 | ---- | |
6 | git-mktag - Creates a tag object | |
7 | ||
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
7791a1d9 | 11 | [verse] |
b1889c36 | 12 | 'git mktag' < signature_file |
2cf565c5 DG |
13 | |
14 | DESCRIPTION | |
15 | ----------- | |
c1bdacf9 DG |
16 | Reads a tag contents on standard input and creates a tag object |
17 | that can also be used to sign other objects. | |
18 | ||
19 | The output is the new tag's <object> identifier. | |
20 | ||
21 | Tag Format | |
22 | ---------- | |
6cfec036 | 23 | A tag signature file has a very simple fixed format: four lines of |
c1bdacf9 DG |
24 | |
25 | object <sha1> | |
26 | type <typename> | |
27 | tag <tagname> | |
6cfec036 | 28 | tagger <tagger> |
c1bdacf9 | 29 | |
6cfec036 JH |
30 | followed by some 'optional' free-form message (some tags created |
31 | by older git may not have `tagger` line). The message, when | |
32 | exists, is separated by a blank line from the header. The | |
33 | message part may contain a signature that git itself doesn't | |
34 | care about, but that can be verified with gpg. | |
2cf565c5 | 35 | |
2cf565c5 DG |
36 | GIT |
37 | --- | |
9e1f0a85 | 38 | Part of the linkgit:git[1] suite |