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

Re: Setting of push.default or confusion about refspecs

From
KSKendall Shaw <kshaw@kendallshaw.com>
Date
Jun 3, 2013, 23:21 UTC
Message-ID
<51AD2502.4010804@kendallshaw.com>
In-Reply-To
<51AD1245.9050202@kendallshaw.com>
On 06/03/2013 03:01 PM, Kendall Shaw wrote:
Show 19 quoted lines
> ... Regarding the upstream branch, I have in .git/config
>
> [remote "origin"]
> url = http://example.com/blah
> fetch = +refs/heads/*:refs/remotes/origin/*
>
> [branch "master"]
> remote = origin
> merge = refs/heads/master
>
> git config -l shows
>
> branch.master.remote=origin
> branch.master.merge=refs/heads/master
>
> When in branch master, is the upstream branch refs/heads/master?
>
> Then, I think I can get push to push to refs/remotes/origin/master by 
> setting push.default to upstream, is that right?

I bit the wax tadpole and tried it. I think setting push.default set to upstream does what I thought.

Kendall
Previous: Kendall Shaw
Message 2 of 2 in “Setting of push.default or confusion about refspecs”
  1. Kendall ShawJun 3, 2013
  2. Kendall ShawJun 3, 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.