threads / bug / 22107

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

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

## tl;dr

One message between Jan 6, 2010 and Jan 6, 2010.

replies: 0people: 1as markdown or json

Zing· Jan 6, 2010, 19:05 UTC · lore

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.

$ 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.