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

Re: [PATCH] branch: make sure the upstream remote is configured

From
Jeff King <peff@peff.net>
Date
Jul 26, 2013, 18:43 UTC
Message-ID
<20130726184311.GA29799@sigill.intra.peff.net>
In-Reply-To
<1374860377-17652-1-git-send-email-cmn@elego.de>
On Fri, Jul 26, 2013 at 07:39:37PM +0200, Carlos Martín Nieto wrote:
Show 7 quoted lines
> A command of e.g.
> 
>     git push --set-upstream /tmp/t master
> 
> will call install_branch_config() with a remote name of "/tmp/t". This
> function will set the 'branch.master.remote' key to, which is
> nonsensical as there is no remote by that name.

Is it nonsensical? It does not make sense for the @{upstream} magic token, because we will not have a branch in tracking branch refs/remotes to point to. But the configuration would still affect how "git pull" chooses a branch to fetch and merge.

I.e., you can currently do:
  git push --set-upstream /tmp/t master
  git pull ;# pulls from /tmp/t master
-Peff
Previous: Carlos Martín NietoNext: Jeff King
Message 2 of 6 in “branch: make sure the upstream remote is configured”
  1. branch: make sure the upstream remote is configuredCarlos Martín Nieto, Jul 26, 2013
  2. Jeff KingJul 26, 2013
  3. Jeff KingJul 26, 2013
  4. Carlos Martín NietoJul 26, 2013
  5. Jeff KingJul 26, 2013
  6. Jeff KingJul 26, 2013

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.