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

[PATCH v2] Documentation/git-pull: clarify configuration

From
Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Date
Nov 10, 2010, 07:13 UTC
Message-ID
<1289373188-32543-1-git-send-email-martin.von.zweigbergk@gmail.com>

The sentence about 'branch.<name>.rebase' refers to the first sentence in the paragraph. Clarify by putting it in a separate paragraph.

Text provided by Jonathan Nieder.
Signed-off-by: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
---
 Documentation/git-pull.txt |   15 +++++++++------
 1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index c50f7dc..055126e 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -92,12 +92,15 @@ include::merge-options.txt[]
 :git-pull: 1
 
 --rebase::
-	Instead of a merge, perform a rebase after fetching.  If
-	there is a remote ref for the upstream branch, and this branch
-	was rebased since last fetched, the rebase uses that information
-	to avoid rebasing non-local changes. To make this the default
-	for branch `<name>`, set configuration `branch.<name>.rebase`
-	to `true`.
+	Instead of merging, rebase the current branch on top of the
+	upstream branch after fetching.  If there is a remote-tracking
+	branch corresponding to the upstream branch and the upstream
+	branch was rebased since last fetched, the rebase uses that
+	information to avoid rebasing non-local changes.
+
+	The default behavior is to merge rather than rebasing, but it
+	can be overridden per branch with the `branch.<name>.rebase`
+	configuration item (see git-config(1)).
 +
 [NOTE]
 This is a potentially _dangerous_ mode of operation.
-- 
1.7.3.2.167.ga361b
Next: Jonathan Nieder
Message 1 of 6 in “Documentation/git-pull: clarify configuration”
  1. Documentation/git-pull: clarify configurationMartin von Zweigbergk, Nov 10, 2010
  2. Jonathan NiederNov 10, 2010
  3. Martin von ZweigbergkNov 11, 2010
  4. Junio C HamanoNov 10, 2010
  5. Martin von ZweigbergkNov 11, 2010
  6. Jonathan NiederNov 11, 2010

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.