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

git pull --all fails (possible options handling bug in git pull?)

From
ZZing <zing@fastmail.fm>
Date
Jan 6, 2010, 19:05 UTC
Message-ID
<hi2mu8$9ob$1@ger.gmane.org>
In 1.6.6, if I do:

$ git pull --all Fetching origin Fetching gnome You asked to pull from the remote '--all', but did not specify a branch. Because this is not the default configured remote for your current branch, you must specify a branch on the command line.

The fetch all remotes works, but shouldn't the "--all" option only apply to the fetch operation? It looks like it's getting noticed by the merge part of the pull.

Message 1 of 1 in “git pull --all fails (possible options handling bug in git pull?)”
  1. ZingJan 6, 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.