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

Unnecessary fetch warning

From
Shawn Pearce <spearce@spearce.org>
Date
Dec 18, 2006, 08:16 UTC
Message-ID
<20061218081631.GA9727@spearce.org>
Current 'next':
  $ git fetch
  Warning: No merge candidate found because value of config option
           "branch.sp/username-reflog.merge" does not match any remote branch fetched.
uhhh.. i asked for a fetch, not a merge.

I have no branch.*.merge or branch.*.remote in my .git/config, and I only use the remote.*.url/remote.*.fetch format for my remote configs.

Commit 62b339a5 added the warning, and its intended for pull, but it is tripping during fetch too.

What about removing this warning from fetch, letting it mark everything as `not-for-merge` and let pull trigger the warning instead?

Next: Josef Weidendorfer
Message 1 of 2 in “Unnecessary fetch warning”
  1. Shawn PearceDec 18, 2006
  2. Move "no merge candidate" warning into git-pullJosef Weidendorfer, Dec 19, 2006

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.