From: Thomas Rast <tr...@inf.ethz.ch> The documentation erroneously used the same wording for both fetch and pull, stating that something will be merged even in git-fetch(1).
In addition, saying that "<ref> is equivalent to <ref>:" doesn't really help anyone who still needs to read manpages. Clarify what is actually going on. Signed-off-by: Thomas Rast <tr...@inf.ethz.ch> Signed-off-by: Jeff King <p...@peff.net> --- Documentation/pull-fetch-param.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt index 94a9d32..6f5ca21 100644 --- a/Documentation/pull-fetch-param.txt +++ b/Documentation/pull-fetch-param.txt @@ -68,6 +68,11 @@ Some short-cut notations are also supported. + * `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`; it requests fetching everything up to the given tag. -* A parameter <ref> without a colon is equivalent to - <ref>: when pulling/fetching, so it merges <ref> into the current - branch without storing the remote branch anywhere locally +ifndef::git-pull +* A parameter <ref> without a colon fetches that ref into FETCH_HEAD, +endif::git-pull +ifdef::git-pull +* A parameter <ref> without a colon merges <ref> into the current + branch, +endif::git-pull + while not storing the branch anywhere locally. -- 1.8.3.rc1.2.g12db477 -- 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