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

DESCRIPTION

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

OPTIONS

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

GIT

121       Part of the git(1) suite
122
123
124
125Git 2.26.2                        2020-04-20                 GIT-FETCH-PACK(1)

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

SEE ALSO

GIT