1--all:: 2 Fetch all remotes. 3 4-a:: 5--append:: 6 Append ref names and object names of fetched refs to the 7 existing contents of `.git/FETCH_HEAD`. Without this 8 option old data in `.git/FETCH_HEAD` will be overwritten. 9 10--depth=<depth>:: 11 Deepen or shorten the history of a 'shallow' repository created by 12 `git clone` with `--depth=<depth>` option (see linkgit:git-clone[1]) 13 to the specified number of commits from the tip of each remote 14 branch history. Tags for the deepened commits are not fetched. 15 16--unshallow:: 17 Convert a shallow repository to a complete one, removing all 18 the limitations imposed by shallow repositories. 19 20ifndef::git-pull[] 21--dry-run:: 22 Show what would be done, without making any changes. 23endif::git-pull[] 24 25-f:: 26--force:: 27 When 'git fetch' is used with `<rbranch>:<lbranch>` 28 refspec, it refuses to update the local branch 29 `<lbranch>` unless the remote branch `<rbranch>` it 30 fetches is a descendant of `<lbranch>`. This option 31 overrides that check. 32 33-k:: 34--keep:: 35 Keep downloaded pack. 36 37ifndef::git-pull[] 38--multiple:: 39 Allow several <repository> and <group> arguments to be 40 specified. No <refspec>s may be specified. 41 42-p:: 43--prune:: 44 After fetching, remove any remote-tracking branches which 45 no longer exist on the remote. 46endif::git-pull[] 47 48ifdef::git-pull[] 49--no-tags:: 50endif::git-pull[] 51ifndef::git-pull[] 52-n:: 53--no-tags:: 54endif::git-pull[] 55 By default, tags that point at objects that are downloaded 56 from the remote repository are fetched and stored locally. 57 This option disables this automatic tag following. The default 58 behavior for a remote may be specified with the remote.<name>.tagopt 59 setting. See linkgit:git-config[1]. 60 61ifndef::git-pull[] 62-t:: 63--tags:: 64 Request that all tags be fetched from the remote in addition 65 to whatever else is being fetched. Its effect is similar to 66 that of the refspec `refs/tags/*:refs/tags/*`. 67 68--recurse-submodules[=yes|on-demand|no]:: 69 This option controls if and under what conditions new commits of 70 populated submodules should be fetched too. It can be used as a 71 boolean option to completely disable recursion when set to 'no' or to 72 unconditionally recurse into all populated submodules when set to 73 'yes', which is the default when this option is used without any 74 value. Use 'on-demand' to only recurse into a populated submodule 75 when the superproject retrieves a commit that updates the submodule's 76 reference to a commit that isn't already in the local submodule 77 clone. 78 79--no-recurse-submodules:: 80 Disable recursive fetching of submodules (this has the same effect as 81 using the '--recurse-submodules=no' option). 82 83--submodule-prefix=<path>:: 84 Prepend <path> to paths printed in informative messages 85 such as "Fetching submodule foo". This option is used 86 internally when recursing over submodules. 87 88--recurse-submodules-default=[yes|on-demand]:: 89 This option is used internally to temporarily provide a 90 non-negative default value for the --recurse-submodules 91 option. All other methods of configuring fetch's submodule 92 recursion (such as settings in linkgit:gitmodules[5] and 93 linkgit:git-config[1]) override this option, as does 94 specifying --[no-]recurse-submodules directly. 95endif::git-pull[] 96 97-u:: 98--update-head-ok:: 99 By default 'git fetch' refuses to update the head which 100 corresponds to the current branch. This flag disables the 101 check. This is purely for the internal use for 'git pull' 102 to communicate with 'git fetch', and unless you are 103 implementing your own Porcelain you are not supposed to 104 use it. 105 106--upload-pack <upload-pack>:: 107 When given, and the repository to fetch from is handled 108 by 'git fetch-pack', '--exec=<upload-pack>' is passed to 109 the command to specify non-default path for the command 110 run on the other end. 111 112ifndef::git-pull[] 113-q:: 114--quiet:: 115 Pass --quiet to git-fetch-pack and silence any other internally 116 used git commands. Progress is not reported to the standard error 117 stream. 118 119-v:: 120--verbose:: 121 Be verbose. 122endif::git-pull[] 123 124--progress:: 125 Progress status is reported on the standard error stream 126 by default when it is attached to a terminal, unless -q 127 is specified. This flag forces progress status even if the 128 standard error stream is not directed to a terminal.