git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 4/5] fetch doc: on pulling multiple refspecs

From
Junio C Hamano <gitster@pobox.com>
Date
May 29, 2014, 22:42 UTC
Message-ID
<1401403350-7122-5-git-send-email-gitster@pobox.com>
In-Reply-To
<1401403350-7122-1-git-send-email-gitster@pobox.com>

Replace desription of old-style "Pull:" lines in remotes/ configuration with modern remote.*.fetch variables.

As this note applies only to "git pull", enable it only in git-pull manual page.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/pull-fetch-param.txt | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt
index e266c2d..ea4c5a6 100644
--- a/Documentation/pull-fetch-param.txt
+++ b/Documentation/pull-fetch-param.txt
@@ -34,22 +34,26 @@ will be needed for such branches.  There is no way to
 determine or declare that a branch will be made available
 in a repository with this behavior; the pulling user simply
 must know this is the expected usage pattern for a branch.
+ifdef::git-pull[]
 +
 [NOTE]
 There is a difference between listing multiple <refspec>
 directly on 'git pull' command line and having multiple
-`Pull:` <refspec> lines for a <repository> and running
+`remote.<repository>.fetch` entries in your configuration
+for a <repository> and running
 'git pull' command without any explicit <refspec> parameters.
 <refspec> listed explicitly on the command line are always
 merged into the current branch after fetching.  In other words,
 if you list more than one remote refs, you would be making
-an Octopus.  While 'git pull' run without any explicit <refspec>
-parameter takes default <refspec>s from `Pull:` lines, it
+an Octopus merge. On the other hand, 'git pull' that is run
+without any explicit <refspec> parameter takes default
+<refspec>s from `remote.<repository>.fetch` configuration, it
 merges only the first <refspec> found into the current branch,
-after fetching all the remote refs.  This is because making an
+after fetching all the remote refs specified.  This is because making an
 Octopus from remote refs is rarely done, while keeping track
 of multiple remote heads in one-go by fetching more than one
 is often useful.
+endif::git-pull[]
 +
 Some short-cut notations are also supported.
 +
-- 
2.0.0-479-g59ac8f9
Previous: Junio C HamanoNext: Junio C Hamano
Message 14 of 15 in “Documentation updates for 'git fetch'”
  1. 0/5 Documentation updates for 'git fetch'Junio C Hamano, May 29, 2014
  2. 1/5 fetch doc: update introductory part for clarityJunio C Hamano, May 29, 2014
  3. Marc BranchaudMay 30, 2014
  4. Junio C HamanoMay 30, 2014
  5. Marc BranchaudMay 30, 2014
  6. Junio C HamanoMay 30, 2014
  7. fetch doc: Move FETCH_HEAD material, and add an example.Marc Branchaud, Jun 2, 2014
  8. Junio C HamanoJun 2, 2014
  9. 2/5 fetch doc: update note on '+' in front of the refspecJunio C Hamano, May 29, 2014
  10. Marc BranchaudMay 30, 2014
  11. Junio C HamanoMay 30, 2014
  12. Marc BranchaudJun 2, 2014
  13. 3/5 fetch doc: remove notes on outdated "mixed layout"Junio C Hamano, May 29, 2014
  14. 4/5 fetch doc: on pulling multiple refspecsJunio C Hamano, May 29, 2014
  15. 5/5 fetch doc: update refspec format descriptionJunio C Hamano, May 29, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.