Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
git-fetch: document automatic tag following.
author
Junio C Hamano
<junkio@cox.net>
Fri, 9 Feb 2007 23:41:35 +0000
(15:41 -0800)
committer
Junio C Hamano
<junkio@cox.net>
Fri, 9 Feb 2007 23:41:35 +0000
(15:41 -0800)
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-fetch.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
ad34a02
)
diff --git
a/Documentation/git-fetch.txt
b/Documentation/git-fetch.txt
index 7ecf2408d6fe060ccf5d179760abe59b708571f0..5fbeab76b7214f871865eaefd5dbe744036676b0 100644
(file)
--- a/
Documentation/git-fetch.txt
+++ b/
Documentation/git-fetch.txt
@@
-20,6
+20,14
@@
The ref names and their object names of fetched refs are stored
in `.git/FETCH_HEAD`. This information is left for a later merge
operation done by "git merge".
in `.git/FETCH_HEAD`. This information is left for a later merge
operation done by "git merge".
+When <refspec> stores the fetched result in tracking branches,
+the tags that point at these branches are automatically
+followed. This is done by first fetching from the remote using
+the given <refspec>s, and if the repository has objects that are
+pointed by remote tags that it does not yet have, then fetch
+those missing tags. If the other end has tags that point at
+branches you are not interested in, you will not get them.
+
OPTIONS
-------
OPTIONS
-------