SYNOPSIS
git-upload-pack [--[no-]strict] [--timeout=<n>] [--stateless-rpc] [--advertise-refs] <directory>
DESCRIPTION
Invoked by git fetch-pack, learns what objects the other side is missing, and sends them after packing.
This command is usually not invoked directly by the end user. The UI for the protocol is on the git fetch-pack side, and the program pair is meant to be used to pull updates from a remote repository. For push operations, see git send-pack.
OPTIONS
- --[no-]strict
-
Do not try <directory>/.git/ if <directory> is no Git directory.
- --timeout=<n>
-
Interrupt transfer after <n> seconds of inactivity.
- --stateless-rpc
-
Perform only a single read-write cycle with stdin and stdout. This fits with the HTTP POST request processing model where a program may read the request, write a response, and must exit.
- --advertise-refs
-
Only the initial ref advertisement is output, and the program exits immediately. This fits with the HTTP GET request model, where no request content is received but a response must be produced.
- <directory>
-
The repository to sync from.
-
GIT_NO_LAZY_FETCH
-
When cloning or fetching from a partial repository (i.e., one itself cloned with
--filter
), the server-sideupload-pack
may need to fetch extra objects from its upstream in order to complete the request. By default,upload-pack
will refuse to perform such a lazy fetch, becausegit fetch
may run arbitrary commands specified in configuration and hooks of the source repository (andupload-pack
tries to be safe to run even in untrusted.git
directories).
This is implemented by having upload-pack
internally set the
GIT_NO_LAZY_FETCH
variable to 1
. If you want to override it
(because you are fetching from a partial clone, and you are sure
you trust it), you can explicitly set GIT_NO_LAZY_FETCH
to
0
.
SEE ALSO
GIT
Part of the git(1) suite