зеркало из https://github.com/microsoft/git.git
git-fetch.txt: document fetch output
This documents the ref update status of fetch. The structure of this output is defined in [1]. The ouput content is refined a bit in [2] [3] [4]. This patch is a copy from git-push.txt, modified a bit because the flag '-' means different things in push (delete) and fetch (tag update). PS. For code archaeologists, the discussion mentioned in [1] is probably [5]. [1]165f390
(git-fetch: more terse fetch output - 2007-11-03) [2]6315472
(fetch: report local storage errors ... - 2008-06-26) [3]f360d84
(builtin-fetch: add --prune option - 2009-11-10) [4]0997ada
(fetch: describe new refs based on where... - 2012-04-16) [5] http://thread.gmane.org/gmane.comp.version-control.git/61657 Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Родитель
05219a1276
Коммит
a52397cce6
|
@ -99,6 +99,52 @@ The latter use of the `remote.<repository>.fetch` values can be
|
||||||
overridden by giving the `--refmap=<refspec>` parameter(s) on the
|
overridden by giving the `--refmap=<refspec>` parameter(s) on the
|
||||||
command line.
|
command line.
|
||||||
|
|
||||||
|
OUTPUT
|
||||||
|
------
|
||||||
|
|
||||||
|
The output of "git fetch" depends on the transport method used; this
|
||||||
|
section describes the output when fetching over the Git protocol
|
||||||
|
(either locally or via ssh) and Smart HTTP protocol.
|
||||||
|
|
||||||
|
The status of the fetch is output in tabular form, with each line
|
||||||
|
representing the status of a single ref. Each line is of the form:
|
||||||
|
|
||||||
|
-------------------------------
|
||||||
|
<flag> <summary> <from> -> <to> [<reason>]
|
||||||
|
-------------------------------
|
||||||
|
|
||||||
|
The status of up-to-date refs is shown only if the --verbose option is
|
||||||
|
used.
|
||||||
|
|
||||||
|
flag::
|
||||||
|
A single character indicating the status of the ref:
|
||||||
|
(space);; for a successfully fetched fast-forward;
|
||||||
|
`+`;; for a successful forced update;
|
||||||
|
`x`;; for a successfully pruned ref;
|
||||||
|
`-`;; for a successful tag update;
|
||||||
|
`*`;; for a successfully fetched new ref;
|
||||||
|
`!`;; for a ref that was rejected or failed to update; and
|
||||||
|
`=`;; for a ref that was up to date and did not need fetching.
|
||||||
|
|
||||||
|
summary::
|
||||||
|
For a successfully fetched ref, the summary shows the old and new
|
||||||
|
values of the ref in a form suitable for using as an argument to
|
||||||
|
`git log` (this is `<old>..<new>` in most cases, and
|
||||||
|
`<old>...<new>` for forced non-fast-forward updates).
|
||||||
|
|
||||||
|
from::
|
||||||
|
The name of the remote ref being fetched from, minus its
|
||||||
|
`refs/<type>/` prefix. In the case of deletion, the name of
|
||||||
|
the remote ref is "(none)".
|
||||||
|
|
||||||
|
to::
|
||||||
|
The name of the local ref being updated, minus its
|
||||||
|
`refs/<type>/` prefix.
|
||||||
|
|
||||||
|
reason::
|
||||||
|
A human-readable explanation. In the case of successfully fetched
|
||||||
|
refs, no explanation is needed. For a failed ref, the reason for
|
||||||
|
failure is described.
|
||||||
|
|
||||||
EXAMPLES
|
EXAMPLES
|
||||||
--------
|
--------
|
||||||
|
|
Загрузка…
Ссылка в новой задаче