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.
34 lines
963 B
Plaintext
34 lines
963 B
Plaintext
git-shell(1)
|
|
============
|
|
|
|
NAME
|
|
----
|
|
git-shell - Restricted login shell for Git-only SSH access
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
'git shell' [-c <command> <argument>]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
A login shell for SSH accounts to provide restricted Git access. When
|
|
'-c' is given, the program executes <command> non-interactively;
|
|
<command> can be one of 'git receive-pack', 'git upload-pack', 'git
|
|
upload-archive', 'cvs server', or a command in COMMAND_DIR. The shell
|
|
is started in interactive mode when no arguments are given; in this
|
|
case, COMMAND_DIR must exist, and any of the executables in it can be
|
|
invoked.
|
|
|
|
'cvs server' is a special command which executes git-cvsserver.
|
|
|
|
COMMAND_DIR is the path "$HOME/git-shell-commands". The user must have
|
|
read and execute permissions to the directory in order to execute the
|
|
programs in it. The programs are executed with a cwd of $HOME, and
|
|
<argument> is parsed as a command-line string.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|