Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.45.2 → 2.47.1 no changes
-
2.45.1
04/29/24
- 2.45.0 no changes
- 2.44.2 no changes
-
2.44.1
04/19/24
- 2.44.0 no changes
- 2.43.5 no changes
-
2.43.4
04/19/24
- 2.43.1 → 2.43.3 no changes
- 2.43.0 no changes
- 2.42.3 no changes
-
2.42.2
04/19/24
- 2.42.1 no changes
- 2.42.0 no changes
- 2.41.2 no changes
-
2.41.1
04/19/24
- 2.41.0 no changes
- 2.40.3 no changes
-
2.40.2
04/19/24
- 2.40.1 no changes
- 2.40.0 no changes
- 2.39.5 no changes
-
2.39.4
04/19/24
- 2.38.1 → 2.39.3 no changes
-
2.38.0
10/02/22
- 2.34.1 → 2.37.7 no changes
-
2.34.0
11/15/21
- 2.21.1 → 2.33.8 no changes
- 2.21.0 no changes
- 2.19.3 → 2.20.5 no changes
-
2.19.2
11/21/18
- 2.11.4 → 2.19.1 no changes
-
2.10.5
09/22/17
- 2.1.4 → 2.9.5 no changes
-
2.0.5
12/17/14
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 not a 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.
- --http-backend-info-refs
-
Used by git-http-backend[1] to serve up
$GIT_URL/info/refs?service=git-upload-packrequests. See "Smart Clients" in gitprotocol-http[5] and "HTTP Transport" in the gitprotocol-v2[5] documentation. Also understood by git-receive-pack[1]. - <directory>
-
The repository to sync from.
ENVIRONMENT
-
GIT_PROTOCOL -
Internal variable used for handshaking the wire protocol. Server admins may need to configure some transports to allow this variable to be passed. See the discussion in git[1].
-
GIT_NO_LAZY_FETCH -
When cloning or fetching from a partial repository (i.e., one itself cloned with
--filter), the server-sideupload-packmay need to fetch extra objects from its upstream in order to complete the request. By default,upload-packwill refuse to perform such a lazy fetch, becausegit fetchmay run arbitrary commands specified in configuration and hooks of the source repository (andupload-packtries to be safe to run even in untrusted.gitdirectories).This is implemented by having
upload-packinternally set theGIT_NO_LAZY_FETCHvariable to1. If you want to override it (because you are fetching from a partial clone, and you are sure you trust it), you can explicitly setGIT_NO_LAZY_FETCHto0.
SECURITY
Most Git commands should not be run in an untrusted .git directory
(see the section SECURITY in git[1]). upload-pack tries to
avoid any dangerous configuration options or hooks from the repository
it’s serving, making it safe to clone an untrusted directory and run
commands on the resulting clone.
For an extra level of safety, you may be able to run upload-pack as an
alternate user. The details will be platform dependent, but on many
systems you can run:
git clone --no-local --upload-pack='sudo -u nobody git-upload-pack' ...
GIT
Part of the git[1] suite
