2005-05-10 23:32:30 +02:00
|
|
|
git-mktag(1)
|
|
|
|
============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2021-01-05 20:42:32 +01:00
|
|
|
git-mktag - Creates a tag object with extra validation
|
2005-05-10 23:32:30 +02:00
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2011-07-02 04:38:26 +02:00
|
|
|
[verse]
|
usage: do not insist that standard input must come from a file
The synopsys text and the usage string of subcommands that read list
of things from the standard input are often shown like this:
git gostak [--distim] < <list-of-doshes>
This is problematic in a number of ways:
* The way to use these commands is more often to feed them the
output from another command, not feed them from a file.
* Manual pages outside Git, commands that operate on the data read
from the standard input, e.g "sort", "grep", "sed", etc., are not
described with such a "< redirection-from-file" in their synopsys
text. Our doing so introduces inconsistency.
* We do not insist on where the output should go, by saying
git gostak [--distim] < <list-of-doshes> > <output>
* As it is our convention to enclose placeholders inside <braket>,
the redirection operator followed by a placeholder filename
becomes very hard to read, both in the documentation and in the
help text.
Let's clean them all up, after making sure that the documentation
clearly describes the modes that take information from the standard
input and what kind of things are expected on the input.
[jc: stole example for fmt-merge-msg from Jonathan]
Helped-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-10-16 20:27:42 +02:00
|
|
|
'git mktag'
|
2005-05-10 23:32:30 +02:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2005-05-10 23:32:38 +02:00
|
|
|
|
2021-01-05 20:42:32 +01:00
|
|
|
Reads a tag contents on standard input and creates a tag object. The
|
|
|
|
output is the new tag's <object> identifier.
|
|
|
|
|
|
|
|
This command is mostly equivalent to linkgit:git-hash-object[1]
|
|
|
|
invoked with `-t tag -w --stdin`. I.e. both of these will create and
|
|
|
|
write a tag found in `my-tag`:
|
|
|
|
|
|
|
|
git mktag <my-tag
|
|
|
|
git hash-object -t tag -w --stdin <my-tag
|
|
|
|
|
|
|
|
The difference is that mktag will die before writing the tag if the
|
|
|
|
tag doesn't pass a sanity check.
|
2005-05-10 23:32:38 +02:00
|
|
|
|
|
|
|
Tag Format
|
|
|
|
----------
|
usage: do not insist that standard input must come from a file
The synopsys text and the usage string of subcommands that read list
of things from the standard input are often shown like this:
git gostak [--distim] < <list-of-doshes>
This is problematic in a number of ways:
* The way to use these commands is more often to feed them the
output from another command, not feed them from a file.
* Manual pages outside Git, commands that operate on the data read
from the standard input, e.g "sort", "grep", "sed", etc., are not
described with such a "< redirection-from-file" in their synopsys
text. Our doing so introduces inconsistency.
* We do not insist on where the output should go, by saying
git gostak [--distim] < <list-of-doshes> > <output>
* As it is our convention to enclose placeholders inside <braket>,
the redirection operator followed by a placeholder filename
becomes very hard to read, both in the documentation and in the
help text.
Let's clean them all up, after making sure that the documentation
clearly describes the modes that take information from the standard
input and what kind of things are expected on the input.
[jc: stole example for fmt-merge-msg from Jonathan]
Helped-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-10-16 20:27:42 +02:00
|
|
|
A tag signature file, to be fed to this command's standard input,
|
|
|
|
has a very simple fixed format: four lines of
|
2005-05-10 23:32:38 +02:00
|
|
|
|
2020-12-23 02:35:46 +01:00
|
|
|
object <hash>
|
2005-05-10 23:32:38 +02:00
|
|
|
type <typename>
|
|
|
|
tag <tagname>
|
2007-06-11 01:00:36 +02:00
|
|
|
tagger <tagger>
|
2005-05-10 23:32:38 +02:00
|
|
|
|
2007-06-11 01:00:36 +02:00
|
|
|
followed by some 'optional' free-form message (some tags created
|
2020-12-23 02:35:47 +01:00
|
|
|
by older Git may not have `tagger` line). The message, when it
|
2007-06-11 01:00:36 +02:00
|
|
|
exists, is separated by a blank line from the header. The
|
2013-01-21 20:17:53 +01:00
|
|
|
message part may contain a signature that Git itself doesn't
|
2007-06-11 01:00:36 +02:00
|
|
|
care about, but that can be verified with gpg.
|
2005-05-10 23:32:30 +02:00
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 09:07:32 +02:00
|
|
|
Part of the linkgit:git[1] suite
|