Junio C Hamano <gitster-v...@pobox.com> writes: > I also agree that the documentation is misstated; "remote-tracking branch" > may have been a convenient and well understood phrase for whoever wrote > that part, but the --prune is designed to cull extra refs in the > hierarchies into > which refs would be fetched if counterparts existed on the other side, so > culling tags that do not exist on the remote side should also be described.
(gleaning-leftovers mode) Documentation/fetch-options.txt | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt index ba1fe49..a6c581b 100644 --- a/Documentation/fetch-options.txt +++ b/Documentation/fetch-options.txt @@ -41,8 +41,20 @@ ifndef::git-pull -p:: --prune:: - After fetching, remove any remote-tracking branches which - no longer exist on the remote. + + After fetching, remove any local ref that was not updated + only because the remote ref that was supposed to update it + was missing. ++ +For example, `git fetch origin refs/heads/*:refs/remotes/origin/*` +tries to update local `refs/remotes/origin/frotz` if `origin` has +`refs/heads/frotz`. With this option, `refs/remotes/origin/frotz` +will be removed from our repository if `origin` does not have +`refs/heads/frotz`. ++ +This is used to remove remote-tracking branches which no longer +exist on the remote. + endif::git-pull ifdef::git-pull -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html