git-fetch-pack(1)

1GIT-FETCH-PACK(1)                 Git Manual                 GIT-FETCH-PACK(1)
2
3
4

NAME

6       git-fetch-pack - Receive missing objects from another repository
7

SYNOPSIS

9       git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag]
10               [--upload-pack=<git-upload-pack>]
11               [--depth=<n>] [--no-progress]
12               [-v] <repository> [<refs>...]
13
14

DESCRIPTION

16       Usually you would want to use git fetch, which is a higher level
17       wrapper of this command, instead.
18
19       Invokes git-upload-pack on a possibly remote repository and asks it to
20       send objects missing from this repository, to update the named heads.
21       The list of commits available locally is found out by scanning the
22       local refs/ hierarchy and sent to git-upload-pack running on the other
23       end.
24
25       This command degenerates to download everything to complete the asked
26       refs from the remote side when the local side does not have a common
27       ancestor commit.
28

OPTIONS

30       --all
31           Fetch all remote refs.
32
33       --stdin
34           Take the list of refs from stdin, one per line. If there are refs
35           specified on the command line in addition to this option, then the
36           refs from stdin are processed after those on the command line.
37
38           If --stateless-rpc is specified together with this option then the
39           list of refs must be in packet format (pkt-line). Each ref must be
40           in a separate packet, and the list must end with a flush packet.
41
42       -q, --quiet
43           Pass -q flag to git unpack-objects; this makes the cloning process
44           less verbose.
45
46       -k, --keep
47           Do not invoke git unpack-objects on received data, but create a
48           single packfile out of it instead, and store it in the object
49           database. If provided twice then the pack is locked against
50           repacking.
51
52       --thin
53           Fetch a "thin" pack, which records objects in deltified form based
54           on objects not included in the pack to reduce network traffic.
55
56       --include-tag
57           If the remote side supports it, annotated tags objects will be
58           downloaded on the same connection as the other objects if the
59           object the tag references is downloaded. The caller must otherwise
60           determine the tags this option made available.
61
62       --upload-pack=<git-upload-pack>
63           Use this to specify the path to git-upload-pack on the remote side,
64           if is not found on your $PATH. Installations of sshd ignores the
65           user’s environment setup scripts for login shells (e.g.
66           .bash_profile) and your privately installed git may not be found on
67           the system default $PATH. Another workaround suggested is to set up
68           your $PATH in ".bashrc", but this flag is for people who do not
69           want to pay the overhead for non-interactive shells by having a
70           lean .bashrc file (they set most of the things up in
71           .bash_profile).
72
73       --exec=<git-upload-pack>
74           Same as --upload-pack=<git-upload-pack>.
75
76       --depth=<n>
77           Limit fetching to ancestor-chains not longer than n.
78           git-upload-pack treats the special depth 2147483647 as infinite
79           even if there is an ancestor-chain that long.
80
81       --shallow-since=<date>
82           Deepen or shorten the history of a shallow repository to include
83           all reachable commits after <date>.
84
85       --shallow-exclude=<revision>
86           Deepen or shorten the history of a shallow repository to exclude
87           commits reachable from a specified remote branch or tag. This
88           option can be specified multiple times.
89
90       --deepen-relative
91           Argument --depth specifies the number of commits from the current
92           shallow boundary instead of from the tip of each remote branch
93           history.
94
95       --no-progress
96           Do not show the progress.
97
98       --check-self-contained-and-connected
99           Output "connectivity-ok" if the received pack is self-contained and
100           connected.
101
102       -v
103           Run verbosely.
104
105       <repository>
106           The URL to the remote repository.
107
108       <refs>...
109           The remote heads to update from. This is relative to $GIT_DIR (e.g.
110           "HEAD", "refs/heads/master"). When unspecified, update from all
111           heads the remote side has.
112
113           If the remote has enabled the options
114           uploadpack.allowTipSHA1InWant, uploadpack.allowReachableSHA1InWant,
115           or uploadpack.allowAnySHA1InWant, they may alternatively be 40-hex
116           sha1s present on the remote.
117

GIT

122       Part of the git(1) suite
123
124
125
126Git 2.24.1                        12/10/2019                 GIT-FETCH-PACK(1)

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

SEE ALSO

GIT