mirror of
https://github.com/git/git.git
synced 2024-11-16 22:14:53 +01:00
48bb914ed6
The point of these sections is generally to:
1. Give credit where it is due.
2. Give the reader an idea of where to ask questions or
file bug reports.
But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame. For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.
So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.
Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
37 lines
798 B
Text
37 lines
798 B
Text
git-mktag(1)
|
|
============
|
|
|
|
NAME
|
|
----
|
|
git-mktag - Creates a tag object
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git mktag' < signature_file
|
|
|
|
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 linkgit:git[1] suite
|