I was reading the git pull documentation and discovered an outdated example description. While reading the git fetch documentation to confirm the behaviour described ingit pull was indeed wrong, I figured it would be easier to refer directly to the "Configured remote-tracking branches" section in git fetch from the git pull documentation, just as in git fetch. Philippe Blain (2): pull doc: refer to a specific section in 'fetch' doc pull doc: correct outdated description of an example Documentation/git-pull.txt | 6 +++--- Documentation/pull-fetch-param.txt | 3 ++- 2 files changed, 5 insertions(+), 4 deletions(-) base-commit: 9fadedd637b312089337d73c3ed8447e9f0aa775 Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-751%2Fphil-blain%2Fdoc-pull-update-remote-tracking-v1 Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-751/phil-blain/doc-pull-update-remote-tracking-v1 Pull-Request: https://github.com/git/git/pull/751 -- gitgitgadget
