From: "Philippe Blain via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Marc Branchaud <marcnarc@xiplink.com>,
Clemens Buchacher <drizzd@gmx.net>,
Philippe Blain <levraiphilippeblain@gmail.com>
Subject: [PATCH 0/2] git-pull.txt: correct outdated example + link to specific 'git fetch' section
Date: Sun, 05 Apr 2020 15:50:17 +0000 [thread overview]
Message-ID: <pull.751.git.git.1586101819.gitgitgadget@gmail.com> (raw)
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
next reply other threads:[~2020-04-05 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 15:50 Philippe Blain via GitGitGadget [this message]
2020-04-05 15:50 ` [PATCH 1/2] pull doc: refer to a specific section in 'fetch' doc Philippe Blain via GitGitGadget
2020-04-06 20:19 ` Jeff King
2020-04-16 12:39 ` Philippe Blain
2020-04-05 15:50 ` [PATCH 2/2] pull doc: correct outdated description of an example Philippe Blain via GitGitGadget
2020-04-06 20:22 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.751.git.git.1586101819.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=drizzd@gmx.net \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.com \
--cc=marcnarc@xiplink.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.