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

Re: [PATCH] pull --all: fix error message when current branch is not tracking remote branch

From
Michael Lukashov <michael.lukashov@gmail.com>
Date
Mar 8, 2010, 20:26 UTC
Message-ID
<63cde7731003081226hb27c705l9038f2dccfd1c042@mail.gmail.com>
In-Reply-To
<1267566741-5784-1-git-send-email-michael.lukashov@gmail.com>

No-one ever interested? Thought it's useful improvement.

Instead of above-mentioned confusing message, you get much more clearer explanation:

You asked me to pull without telling me which branch you want to merge with, and 'branch.<>.merge' in your configuration file does not tell me, either. Please specify which branch you want to use on the command line and try again (e.g. 'git pull <repository> <refspec>'). See git-pull(1) for details.

...
Previous: Michael Lukashov
Message 2 of 2 in “pull --all: fix error message when current branch is not tracking remote branch”
  1. pull --all: fix error message when current branch is not tracking remote branchMichael Lukashov, Mar 2, 2010
  2. Michael LukashovMar 8, 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.