2009-11-09 21:09:56 +01:00
|
|
|
--all::
|
|
|
|
|
Fetch all remotes.
|
|
|
|
|
|
2008-06-08 03:36:09 +02:00
|
|
|
-a::
|
|
|
|
|
--append::
|
2005-11-07 06:30:56 +01:00
|
|
|
Append ref names and object names of fetched refs to the
|
|
|
|
|
existing contents of `.git/FETCH_HEAD`. Without this
|
|
|
|
|
option old data in `.git/FETCH_HEAD` will be overwritten.
|
|
|
|
|
|
2009-10-21 22:07:49 +02:00
|
|
|
--depth=<depth>::
|
2016-01-08 10:32:52 +01:00
|
|
|
Limit fetching to the specified number of commits from the tip of
|
|
|
|
|
each remote branch history. If fetching to a 'shallow' repository
|
|
|
|
|
created by `git clone` with `--depth=<depth>` option (see
|
|
|
|
|
linkgit:git-clone[1]), deepen or shorten the history to the specified
|
|
|
|
|
number of commits. Tags for the deepened commits are not fetched.
|
2006-01-20 19:05:24 +01:00
|
|
|
|
fetch, upload-pack: --deepen=N extends shallow boundary by N commits
In git-fetch, --depth argument is always relative with the latest
remote refs. This makes it a bit difficult to cover this use case,
where the user wants to make the shallow history, say 3 levels
deeper. It would work if remote refs have not moved yet, but nobody
can guarantee that, especially when that use case is performed a
couple months after the last clone or "git fetch --depth". Also,
modifying shallow boundary using --depth does not work well with
clones created by --since or --not.
This patch fixes that. A new argument --deepen=<N> will add <N> more (*)
parent commits to the current history regardless of where remote refs
are.
Have/Want negotiation is still respected. So if remote refs move, the
server will send two chunks: one between "have" and "want" and another
to extend shallow history. In theory, the client could send no "want"s
in order to get the second chunk only. But the protocol does not allow
that. Either you send no want lines, which means ls-remote; or you
have to send at least one want line that carries deep-relative to the
server..
The main work was done by Dongcan Jiang. I fixed it up here and there.
And of course all the bugs belong to me.
(*) We could even support --deepen=<N> where <N> is negative. In that
case we can cut some history from the shallow clone. This operation
(and --depth=<shorter depth>) does not require interaction with remote
side (and more complicated to implement as a result).
Helped-by: Duy Nguyen <pclouds@gmail.com>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Dongcan Jiang <dongcan.jiang@gmail.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-06-12 12:54:09 +02:00
|
|
|
--deepen=<depth>::
|
|
|
|
|
Similar to --depth, except it specifies the number of commits
|
|
|
|
|
from the current shallow boundary instead of from the tip of
|
|
|
|
|
each remote branch history.
|
|
|
|
|
|
2016-06-12 12:53:59 +02:00
|
|
|
--shallow-since=<date>::
|
|
|
|
|
Deepen or shorten the history of a shallow repository to
|
|
|
|
|
include all reachable commits after <date>.
|
|
|
|
|
|
2016-06-12 12:54:04 +02:00
|
|
|
--shallow-exclude=<revision>::
|
|
|
|
|
Deepen or shorten the history of a shallow repository to
|
|
|
|
|
exclude commits reachable from a specified remote branch or tag.
|
|
|
|
|
This option can be specified multiple times.
|
|
|
|
|
|
2013-01-11 10:05:46 +01:00
|
|
|
--unshallow::
|
2013-12-05 14:02:41 +01:00
|
|
|
If the source repository is complete, convert a shallow
|
|
|
|
|
repository to a complete one, removing all the limitations
|
|
|
|
|
imposed by shallow repositories.
|
|
|
|
|
+
|
|
|
|
|
If the source repository is shallow, fetch as much as possible so that
|
|
|
|
|
the current repository has the same history as the source repository.
|
2013-01-11 10:05:46 +01:00
|
|
|
|
2013-12-05 14:02:42 +01:00
|
|
|
--update-shallow::
|
|
|
|
|
By default when fetching from a shallow repository,
|
|
|
|
|
`git fetch` refuses refs that require updating
|
|
|
|
|
.git/shallow. This option updates .git/shallow and accept such
|
|
|
|
|
refs.
|
2013-01-11 10:05:46 +01:00
|
|
|
|
2018-07-03 00:39:44 +02:00
|
|
|
--negotiation-tip=<commit|glob>::
|
|
|
|
|
By default, Git will report, to the server, commits reachable
|
|
|
|
|
from all local refs to find common commits in an attempt to
|
|
|
|
|
reduce the size of the to-be-received packfile. If specified,
|
|
|
|
|
Git will only report commits reachable from the given tips.
|
|
|
|
|
This is useful to speed up fetches when the user knows which
|
|
|
|
|
local ref is likely to have commits in common with the
|
|
|
|
|
upstream ref being fetched.
|
|
|
|
|
+
|
|
|
|
|
This option may be specified more than once; if so, Git will report
|
|
|
|
|
commits reachable from any of the given commits.
|
|
|
|
|
+
|
|
|
|
|
The argument to this option may be a glob on ref names, a ref, or the (possibly
|
|
|
|
|
abbreviated) SHA-1 of a commit. Specifying a glob is equivalent to specifying
|
|
|
|
|
this option multiple times, one for each matching ref name.
|
|
|
|
|
|
2009-11-10 09:19:43 +01:00
|
|
|
ifndef::git-pull[]
|
|
|
|
|
--dry-run::
|
|
|
|
|
Show what would be done, without making any changes.
|
|
|
|
|
endif::git-pull[]
|
|
|
|
|
|
2008-06-08 03:36:09 +02:00
|
|
|
-f::
|
|
|
|
|
--force::
|
2010-01-10 00:33:00 +01:00
|
|
|
When 'git fetch' is used with `<rbranch>:<lbranch>`
|
2005-12-01 21:24:51 +01:00
|
|
|
refspec, it refuses to update the local branch
|
|
|
|
|
`<lbranch>` unless the remote branch `<rbranch>` it
|
|
|
|
|
fetches is a descendant of `<lbranch>`. This option
|
|
|
|
|
overrides that check.
|
2005-11-07 06:30:56 +01:00
|
|
|
|
2009-10-21 22:07:49 +02:00
|
|
|
-k::
|
|
|
|
|
--keep::
|
|
|
|
|
Keep downloaded pack.
|
|
|
|
|
|
2009-11-09 21:10:32 +01:00
|
|
|
ifndef::git-pull[]
|
|
|
|
|
--multiple::
|
|
|
|
|
Allow several <repository> and <group> arguments to be
|
|
|
|
|
specified. No <refspec>s may be specified.
|
2009-11-10 09:15:47 +01:00
|
|
|
|
2010-07-13 14:01:40 +02:00
|
|
|
-p::
|
2009-11-10 09:15:47 +01:00
|
|
|
--prune::
|
2016-06-14 01:58:51 +02:00
|
|
|
Before fetching, remove any remote-tracking references that no
|
fetch --prune: prune only based on explicit refspecs
The old behavior of "fetch --prune" was to prune whatever was being
fetched. In particular, "fetch --prune --tags" caused tags not only
to be fetched, but also to be pruned. This is inappropriate because
there is only one tags namespace that is shared among the local
repository and all remotes. Therefore, if the user defines a local
tag and then runs "git fetch --prune --tags", then the local tag is
deleted. Moreover, "--prune" and "--tags" can also be configured via
fetch.prune / remote.<name>.prune and remote.<name>.tagopt, making it
even less obvious that an invocation of "git fetch" could result in
tag lossage.
Since the command "git remote update" invokes "git fetch", it had the
same problem.
The command "git remote prune", on the other hand, disregarded the
setting of remote.<name>.tagopt, and so its behavior was inconsistent
with that of the other commands.
So the old behavior made it too easy to lose tags. To fix this
problem, change "fetch --prune" to prune references based only on
refspecs specified explicitly by the user, either on the command line
or via remote.<name>.fetch. Thus, tags are no longer made subject to
pruning by the --tags option or the remote.<name>.tagopt setting.
However, tags *are* still subject to pruning if they are fetched as
part of a refspec, and that is good. For example:
* On the command line,
git fetch --prune 'refs/tags/*:refs/tags/*'
causes tags, and only tags, to be fetched and pruned, and is
therefore a simple way for the user to get the equivalent of the old
behavior of "--prune --tag".
* For a remote that was configured with the "--mirror" option, the
configuration is set to include
[remote "name"]
fetch = +refs/*:refs/*
, which causes tags to be subject to pruning along with all other
references. This is the behavior that will typically be desired for
a mirror.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-10-30 06:33:00 +01:00
|
|
|
longer exist on the remote. Tags are not subject to pruning
|
|
|
|
|
if they are fetched only because of the default tag
|
|
|
|
|
auto-following or due to a --tags option. However, if tags
|
|
|
|
|
are fetched due to an explicit refspec (either on the command
|
|
|
|
|
line or in the remote configuration, for example if the remote
|
|
|
|
|
was cloned with the --mirror option), then they are also
|
fetch: add a --prune-tags option and fetch.pruneTags config
Add a --prune-tags option to git-fetch, along with fetch.pruneTags
config option and a -P shorthand (-p is --prune). This allows for
doing any of:
git fetch -p -P
git fetch --prune --prune-tags
git fetch -p -P origin
git fetch --prune --prune-tags origin
Or simply:
git config fetch.prune true &&
git config fetch.pruneTags true &&
git fetch
Instead of the much more verbose:
git fetch --prune origin 'refs/tags/*:refs/tags/*' '+refs/heads/*:refs/remotes/origin/*'
Before this feature it was painful to support the use-case of pulling
from a repo which is having both its branches *and* tags deleted
regularly, and have our local references to reflect upstream.
At work we create deployment tags in the repo for each rollout, and
there's *lots* of those, so they're archived within weeks for
performance reasons.
Without this change it's hard to centrally configure such repos in
/etc/gitconfig (on servers that are only used for working with
them). You need to set fetch.prune=true globally, and then for each
repo:
git -C {} config --replace-all remote.origin.fetch "refs/tags/*:refs/tags/*" "^\+*refs/tags/\*:refs/tags/\*$"
Now I can simply set fetch.pruneTags=true in /etc/gitconfig as well,
and users running "git pull" will automatically get the pruning
semantics I want.
Even though "git remote" has corresponding "prune" and "update
--prune" subcommands I'm intentionally not adding a corresponding
prune-tags or "update --prune --prune-tags" mode to that command.
It's advertised (as noted in my recent "git remote doc: correct
dangerous lies about what prune does") as only modifying remote
tracking references, whereas any --prune-tags option is always going
to modify what from the user's perspective is a local copy of the tag,
since there's no such thing as a remote tracking tag.
Ideally add_prune_tags_to_fetch_refspec() would be something that
would use ALLOC_GROW() to grow the 'fetch` member of the 'remote'
struct. Instead I'm realloc-ing remote->fetch and adding the
tag_refspec to the end.
The reason is that parse_{fetch,push}_refspec which allocate the
refspec (ultimately remote->fetch) struct are called many places that
don't have access to a 'remote' struct. It would be hard to change all
their callsites to be amenable to carry around the bookkeeping
variables required for dynamic allocation.
All the other callers of the API first incrementally construct the
string version of the refspec in remote->fetch_refspec via
add_fetch_refspec(), before finally calling parse_fetch_refspec() via
some variation of remote_get().
It's less of a pain to deal with the one special case that needs to
modify already constructed refspecs than to chase down and change all
the other callsites. The API I'm adding is intentionally not
generalized because if we add more of these we'd probably want to
re-visit how this is done.
See my "Re: [BUG] git remote prune removes local tags, depending on
fetch config" (87po6ahx87.fsf@evledraar.gmail.com;
https://public-inbox.org/git/87po6ahx87.fsf@evledraar.gmail.com/) for
more background info.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-02-09 21:32:15 +01:00
|
|
|
subject to pruning. Supplying `--prune-tags` is a shorthand for
|
|
|
|
|
providing the tag refspec.
|
|
|
|
|
+
|
|
|
|
|
See the PRUNING section below for more details.
|
|
|
|
|
|
|
|
|
|
-P::
|
|
|
|
|
--prune-tags::
|
|
|
|
|
Before fetching, remove any local tags that no longer exist on
|
|
|
|
|
the remote if `--prune` is enabled. This option should be used
|
|
|
|
|
more carefully, unlike `--prune` it will remove any local
|
|
|
|
|
references (local tags) that have been created. This option is
|
|
|
|
|
a shorthand for providing the explicit tag refspec along with
|
|
|
|
|
`--prune`, see the discussion about that in its documentation.
|
2018-02-09 21:32:13 +01:00
|
|
|
+
|
|
|
|
|
See the PRUNING section below for more details.
|
|
|
|
|
|
2009-11-09 21:10:32 +01:00
|
|
|
endif::git-pull[]
|
|
|
|
|
|
2008-01-25 11:17:38 +01:00
|
|
|
ifndef::git-pull[]
|
2008-06-08 03:36:09 +02:00
|
|
|
-n::
|
2008-01-25 11:17:38 +01:00
|
|
|
endif::git-pull[]
|
2013-10-30 06:33:05 +01:00
|
|
|
--no-tags::
|
2008-01-25 11:17:38 +01:00
|
|
|
By default, tags that point at objects that are downloaded
|
|
|
|
|
from the remote repository are fetched and stored locally.
|
2010-08-12 00:57:20 +02:00
|
|
|
This option disables this automatic tag following. The default
|
2015-03-11 21:32:45 +01:00
|
|
|
behavior for a remote may be specified with the remote.<name>.tagOpt
|
2010-08-12 00:57:20 +02:00
|
|
|
setting. See linkgit:git-config[1].
|
2006-01-07 09:48:04 +01:00
|
|
|
|
2010-11-03 21:55:48 +01:00
|
|
|
ifndef::git-pull[]
|
2014-05-30 00:21:31 +02:00
|
|
|
--refmap=<refspec>::
|
|
|
|
|
When fetching refs listed on the command line, use the
|
|
|
|
|
specified refspec (can be given more than once) to map the
|
|
|
|
|
refs to remote-tracking branches, instead of the values of
|
|
|
|
|
`remote.*.fetch` configuration variables for the remote
|
|
|
|
|
repository. See section on "Configured Remote-tracking
|
|
|
|
|
Branches" for details.
|
|
|
|
|
|
2008-06-08 03:36:09 +02:00
|
|
|
-t::
|
|
|
|
|
--tags::
|
fetch --prune: prune only based on explicit refspecs
The old behavior of "fetch --prune" was to prune whatever was being
fetched. In particular, "fetch --prune --tags" caused tags not only
to be fetched, but also to be pruned. This is inappropriate because
there is only one tags namespace that is shared among the local
repository and all remotes. Therefore, if the user defines a local
tag and then runs "git fetch --prune --tags", then the local tag is
deleted. Moreover, "--prune" and "--tags" can also be configured via
fetch.prune / remote.<name>.prune and remote.<name>.tagopt, making it
even less obvious that an invocation of "git fetch" could result in
tag lossage.
Since the command "git remote update" invokes "git fetch", it had the
same problem.
The command "git remote prune", on the other hand, disregarded the
setting of remote.<name>.tagopt, and so its behavior was inconsistent
with that of the other commands.
So the old behavior made it too easy to lose tags. To fix this
problem, change "fetch --prune" to prune references based only on
refspecs specified explicitly by the user, either on the command line
or via remote.<name>.fetch. Thus, tags are no longer made subject to
pruning by the --tags option or the remote.<name>.tagopt setting.
However, tags *are* still subject to pruning if they are fetched as
part of a refspec, and that is good. For example:
* On the command line,
git fetch --prune 'refs/tags/*:refs/tags/*'
causes tags, and only tags, to be fetched and pruned, and is
therefore a simple way for the user to get the equivalent of the old
behavior of "--prune --tag".
* For a remote that was configured with the "--mirror" option, the
configuration is set to include
[remote "name"]
fetch = +refs/*:refs/*
, which causes tags to be subject to pruning along with all other
references. This is the behavior that will typically be desired for
a mirror.
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-10-30 06:33:00 +01:00
|
|
|
Fetch all tags from the remote (i.e., fetch remote tags
|
|
|
|
|
`refs/tags/*` into local tags with the same name), in addition
|
|
|
|
|
to whatever else would otherwise be fetched. Using this
|
|
|
|
|
option alone does not subject tags to pruning, even if --prune
|
|
|
|
|
is used (though tags may be pruned anyway if they are also the
|
2016-06-28 13:40:11 +02:00
|
|
|
destination of an explicit refspec; see `--prune`).
|
2005-11-07 06:30:56 +01:00
|
|
|
|
2011-03-06 23:11:21 +01:00
|
|
|
--recurse-submodules[=yes|on-demand|no]::
|
|
|
|
|
This option controls if and under what conditions new commits of
|
|
|
|
|
populated submodules should be fetched too. It can be used as a
|
|
|
|
|
boolean option to completely disable recursion when set to 'no' or to
|
|
|
|
|
unconditionally recurse into all populated submodules when set to
|
|
|
|
|
'yes', which is the default when this option is used without any
|
|
|
|
|
value. Use 'on-demand' to only recurse into a populated submodule
|
|
|
|
|
when the superproject retrieves a commit that updates the submodule's
|
2011-03-06 23:12:58 +01:00
|
|
|
reference to a commit that isn't already in the local submodule
|
|
|
|
|
clone.
|
2011-03-06 23:11:21 +01:00
|
|
|
|
2015-12-16 01:04:12 +01:00
|
|
|
-j::
|
|
|
|
|
--jobs=<n>::
|
|
|
|
|
Number of parallel children to be used for fetching submodules.
|
|
|
|
|
Each will fetch from different submodules, such that fetching many
|
|
|
|
|
submodules will be faster. By default submodules will be fetched
|
|
|
|
|
one at a time.
|
|
|
|
|
|
2011-03-06 23:11:21 +01:00
|
|
|
--no-recurse-submodules::
|
|
|
|
|
Disable recursive fetching of submodules (this has the same effect as
|
2016-06-28 13:40:11 +02:00
|
|
|
using the `--recurse-submodules=no` option).
|
2010-11-12 13:54:52 +01:00
|
|
|
|
|
|
|
|
--submodule-prefix=<path>::
|
|
|
|
|
Prepend <path> to paths printed in informative messages
|
|
|
|
|
such as "Fetching submodule foo". This option is used
|
|
|
|
|
internally when recursing over submodules.
|
2011-03-06 23:10:46 +01:00
|
|
|
|
|
|
|
|
--recurse-submodules-default=[yes|on-demand]::
|
|
|
|
|
This option is used internally to temporarily provide a
|
|
|
|
|
non-negative default value for the --recurse-submodules
|
|
|
|
|
option. All other methods of configuring fetch's submodule
|
|
|
|
|
recursion (such as settings in linkgit:gitmodules[5] and
|
|
|
|
|
linkgit:git-config[1]) override this option, as does
|
|
|
|
|
specifying --[no-]recurse-submodules directly.
|
2010-11-12 13:54:52 +01:00
|
|
|
endif::git-pull[]
|
2005-11-07 06:30:56 +01:00
|
|
|
|
2008-06-08 03:36:09 +02:00
|
|
|
-u::
|
|
|
|
|
--update-head-ok::
|
2010-01-10 00:33:00 +01:00
|
|
|
By default 'git fetch' refuses to update the head which
|
2005-11-07 06:30:56 +01:00
|
|
|
corresponds to the current branch. This flag disables the
|
2010-01-10 00:33:00 +01:00
|
|
|
check. This is purely for the internal use for 'git pull'
|
|
|
|
|
to communicate with 'git fetch', and unless you are
|
2007-01-02 00:07:35 +01:00
|
|
|
implementing your own Porcelain you are not supposed to
|
|
|
|
|
use it.
|
2006-01-07 09:48:04 +01:00
|
|
|
|
2009-10-21 22:07:49 +02:00
|
|
|
--upload-pack <upload-pack>::
|
|
|
|
|
When given, and the repository to fetch from is handled
|
2016-06-28 13:40:11 +02:00
|
|
|
by 'git fetch-pack', `--exec=<upload-pack>` is passed to
|
2009-10-21 22:07:49 +02:00
|
|
|
the command to specify non-default path for the command
|
|
|
|
|
run on the other end.
|
|
|
|
|
|
|
|
|
|
ifndef::git-pull[]
|
|
|
|
|
-q::
|
|
|
|
|
--quiet::
|
|
|
|
|
Pass --quiet to git-fetch-pack and silence any other internally
|
2010-02-24 13:50:28 +01:00
|
|
|
used git commands. Progress is not reported to the standard error
|
|
|
|
|
stream.
|
2009-10-21 22:07:49 +02:00
|
|
|
|
|
|
|
|
-v::
|
|
|
|
|
--verbose::
|
|
|
|
|
Be verbose.
|
|
|
|
|
endif::git-pull[]
|
2010-02-24 13:50:28 +01:00
|
|
|
|
|
|
|
|
--progress::
|
|
|
|
|
Progress status is reported on the standard error stream
|
|
|
|
|
by default when it is attached to a terminal, unless -q
|
|
|
|
|
is specified. This flag forces progress status even if the
|
|
|
|
|
standard error stream is not directed to a terminal.
|
2016-02-03 05:09:14 +01:00
|
|
|
|
2018-04-24 00:46:24 +02:00
|
|
|
-o <option>::
|
|
|
|
|
--server-option=<option>::
|
|
|
|
|
Transmit the given string to the server when communicating using
|
|
|
|
|
protocol version 2. The given string must not contain a NUL or LF
|
|
|
|
|
character.
|
|
|
|
|
When multiple `--server-option=<option>` are given, they are all
|
|
|
|
|
sent to the other side in the order listed on the command line.
|
|
|
|
|
|
2016-02-03 05:09:14 +01:00
|
|
|
-4::
|
|
|
|
|
--ipv4::
|
|
|
|
|
Use IPv4 addresses only, ignoring IPv6 addresses.
|
|
|
|
|
|
|
|
|
|
-6::
|
|
|
|
|
--ipv6::
|
|
|
|
|
Use IPv6 addresses only, ignoring IPv4 addresses.
|