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

Re: Bug in git rev-parse @{push}?

From
Jeff King <peff@peff.net>
Date
Nov 3, 2016, 15:54 UTC
Message-ID
<20161103155400.jqzopj5i2rrlj6km@sigill.intra.peff.net>
In-Reply-To
<CAJUoZVbnWzpjzWe_qGZTnX_6N2+OJVG39WYaBgY7OfQBNCg+rg@mail.gmail.com>
On Thu, Nov 03, 2016 at 03:48:50PM +0000, Chris Purcell wrote:
> Thanks, Jeff! If I remove the explicit configuration of remote.pushdefault
> = "origin", I get the same error message as you, so I suspect that's _not_
> the default.

That's really bizarre, because I get the same behavior with or without it set. Not only that, but it shouldn't even come into play, as branch.foo.remote should take precedence anyway.

So now I'm really puzzled.
-Peff
Previous: Chris PurcellNext: Chris Purcell
Message 4 of 7 in “Bug in git rev-parse @{push}?”
  1. Chris PurcellNov 3, 2016
  2. Jeff KingNov 3, 2016
  3. Chris PurcellNov 3, 2016
  4. Jeff KingNov 3, 2016
  5. Chris PurcellNov 3, 2016
  6. Jeff KingNov 3, 2016
  7. Chris PurcellNov 3, 2016

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.