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]
10       [--include-tag] [--upload-pack=<git-upload-pack>] [--depth=<n>]
11       [--no-progress] [-v] [<host>:]<directory> [<refs>...]
12

DESCRIPTION

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

OPTIONS

28       --all
29           Fetch all remote refs.
30
31       -q, --quiet
32           Pass -q flag to git unpack-objects; this makes the cloning process
33           less verbose.
34
35       -k, --keep
36           Do not invoke git unpack-objects on received data, but create a
37           single packfile out of it instead, and store it in the object
38           database. If provided twice then the pack is locked against
39           repacking.
40
41       --thin
42           Fetch a "thin" pack, which records objects in deltified form based
43           on objects not included in the pack to reduce network traffic.
44
45       --include-tag
46           If the remote side supports it, annotated tags objects will be
47           downloaded on the same connection as the other objects if the
48           object the tag references is downloaded. The caller must otherwise
49           determine the tags this option made available.
50
51       --upload-pack=<git-upload-pack>
52           Use this to specify the path to git-upload-pack on the remote side,
53           if is not found on your $PATH. Installations of sshd ignores the
54           user’s environment setup scripts for login shells (e.g.
55           .bash_profile) and your privately installed git may not be found on
56           the system default $PATH. Another workaround suggested is to set up
57           your $PATH in ".bashrc", but this flag is for people who do not
58           want to pay the overhead for non-interactive shells by having a
59           lean .bashrc file (they set most of the things up in
60           .bash_profile).
61
62       --exec=<git-upload-pack>
63           Same as --upload-pack=<git-upload-pack>.
64
65       --depth=<n>
66           Limit fetching to ancestor-chains not longer than n.
67
68       --no-progress
69           Do not show the progress.
70
71       -v
72           Run verbosely.
73
74       <host>
75           A remote host that houses the repository. When this part is
76           specified, git-upload-pack is invoked via ssh.
77
78       <directory>
79           The repository to sync from.
80
81       <refs>...
82           The remote heads to update from. This is relative to $GIT_DIR (e.g.
83           "HEAD", "refs/heads/master"). When unspecified, update from all
84           heads the remote side has.
85

AUTHOR

87       Written by Linus Torvalds <torvalds@osdl.org[1]>
88

DOCUMENTATION

90       Documentation by Junio C Hamano.
91

GIT

93       Part of the git(1) suite
94

NOTES

96        1. torvalds@osdl.org
97           mailto:torvalds@osdl.org
98
99
100
101Git 1.7.1                         08/16/2017                 GIT-FETCH-PACK(1)
Impressum