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

Re: [PATCH v2] remote: qualify "git pull" advice for non-upstream branches

From
Harald Nordgren <haraldnordgren@gmail.com>
Date
May 20, 2026, 06:51 UTC
Message-ID
<CAHwyqnVd+eG14ZO0OE9vRFc03Wj2juMWaj0tfrTBseVgi_QdVw@mail.gmail.com>
In-Reply-To
<xmqqbjeb7qfv.fsf@gitster.g>
Show 9 quoted lines
> Hmph, shouldn't this be done conditionally, though?  Most new users
> follow the recommended pattern to set branch.<name>.merge so that
> "git pull" would do the right thing for them, I presume, even when
> they are using triangular workflow to push to a different remote
> than the remote they pull from, so the new and more verbose message
> would not help the users any more than the existing message, right?
>
> Can the code tell the situation where the extra part of the message
> would help and give it only then?
Yes, that's a good idea.
Harald
Previous: Junio C HamanoNext: Harald Nordgren via GitGitGadget
Message 4 of 9 in “remote: qualify "git pull" advice for non-upstream branches”
  1. remote: qualify "git pull" advice for non-upstream branchesHarald Nordgren via GitGitGadget, May 12, 2026
  2. remote: qualify "git pull" advice for non-upstream branchesHarald Nordgren via GitGitGadget, May 13, 2026
  3. Junio C HamanoMay 19, 2026
  4. Harald NordgrenMay 20, 2026
  5. remote: qualify "git pull" advice for non-upstream compareBranchesHarald Nordgren via GitGitGadget, May 20, 2026
  6. Junio C HamanoMay 21, 2026
  7. remote: qualify "git pull" advice for non-upstream compareBranchesHarald Nordgren via GitGitGadget, May 21, 2026
  8. Junio C HamanoJun 10, 2026
  9. Harald NordgrenJun 10, 2026

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.