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.
28 lines
729 B
Plaintext
28 lines
729 B
Plaintext
git-get-tar-commit-id(1)
|
|
========================
|
|
|
|
NAME
|
|
----
|
|
git-get-tar-commit-id - Extract commit ID from an archive created using git-archive
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git get-tar-commit-id' < <tarfile>
|
|
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
Acts as a filter, extracting the commit ID stored in archives created by
|
|
'git archive'. It reads only the first 1024 bytes of input, thus its
|
|
runtime is not influenced by the size of <tarfile> very much.
|
|
|
|
If no commit ID is found, 'git get-tar-commit-id' quietly exists with a
|
|
return code of 1. This can happen if <tarfile> had not been created
|
|
using 'git archive' or if the first parameter of 'git archive' had been
|
|
a tree ID instead of a commit ID or tag.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|