1GIT-UPLOAD-PACK(1) Git Manual GIT-UPLOAD-PACK(1)
2
3
4
6 git-upload-pack - Send objects packed back to git-fetch-pack
7
9 git-upload-pack [--[no-]strict] [--timeout=<n>] [--stateless-rpc]
10 [--advertise-refs] <directory>
11
13 Invoked by git fetch-pack, learns what objects the other side is
14 missing, and sends them after packing.
15
16 This command is usually not invoked directly by the end user. The UI
17 for the protocol is on the git fetch-pack side, and the program pair is
18 meant to be used to pull updates from a remote repository. For push
19 operations, see git send-pack.
20
22 --[no-]strict
23 Do not try <directory>/.git/ if <directory> is no Git directory.
24
25 --timeout=<n>
26 Interrupt transfer after <n> seconds of inactivity.
27
28 --stateless-rpc
29 Perform only a single read-write cycle with stdin and stdout. This
30 fits with the HTTP POST request processing model where a program
31 may read the request, write a response, and must exit.
32
33 --http-backend-info-refs
34 Used by git-http-backend(1) to serve up
35 $GIT_URL/info/refs?service=git-upload-pack requests. See "Smart
36 Clients" in the HTTP transfer protocols[1] documentation and "HTTP
37 Transport" in the Git Wire Protocol, Version 2[2] documentation.
38 Also understood by git-receive-pack(1).
39
40 <directory>
41 The repository to sync from.
42
44 GIT_PROTOCOL
45 Internal variable used for handshaking the wire protocol. Server
46 admins may need to configure some transports to allow this variable
47 to be passed. See the discussion in git(1).
48
50 gitnamespaces(7)
51
53 Part of the git(1) suite
54
56 1. the HTTP transfer protocols
57 file:///usr/share/doc/git/technical/http-protocol.html
58
59 2. the Git Wire Protocol, Version 2
60 file:///usr/share/doc/git/technical/protocol-v2.html
61
62
63
64Git 2.36.1 2022-05-05 GIT-UPLOAD-PACK(1)