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

Re: with git-next, git pull --rebase can print out "fatal: No such ref: ''" for branches without an upstream

From
SASiddharth Agarwal <sid0@fb.com>
Date
Jan 17, 2014, 02:47 UTC
Message-ID
<52D899CA.5050409@fb.com>
In-Reply-To
<20140117022152.GB12444@sigill.intra.peff.net>
On 01/16/2014 06:21 PM, Jeff King wrote:
Show 6 quoted lines
> On Thu, Jan 16, 2014 at 05:08:14PM -0800, Siddharth Agarwal wrote:
>
>> With git-next, where git pull --rebase can print out "fatal: No such
>> ref: ''" if git pull --rebase is run on branches without an upstream.
> This is already fixed in bb3f458 (rebase: fix fork-point with zero
> arguments, 2014-01-09), I think.

If I'm reading the patch correctly, that only fixes it for git rebase, not for git pull --rebase. git-pull.sh contains a separate invocation of git merge-base --fork-point.

Previous: Jeff KingNext: John Keeping
Message 3 of 9 in “with git-next, git pull --rebase can print out "fatal: No such ref: ''" for branches without an upstream”
  1. Siddharth AgarwalJan 17, 2014
  2. Jeff KingJan 17, 2014
  3. Siddharth AgarwalJan 17, 2014
  4. John KeepingJan 17, 2014
  5. Siddharth AgarwalJan 17, 2014
  6. Junio C HamanoJan 17, 2014
  7. John KeepingJan 17, 2014
  8. pull: suppress error when no remoteref is foundJohn Keeping, Jan 17, 2014
  9. Junio C HamanoJan 17, 2014

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.