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

Re: push.default=upstream doesn't play nicely with remote.pushdefault/branch.*.pushremote

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Sep 11, 2013, 00:38 UTC
Message-ID
<CAMP44s0ZnGAhMv0a4HbVkZ6voRzxrXW-4T6Dj=H3Lb3kGFsOHA@mail.gmail.com>
In-Reply-To
<522F1A61.3010805@gmx.com>
On Tue, Sep 10, 2013 at 8:10 AM, Ximin Luo <infinity0@gmx.com> wrote:
> (Please CC me as I am not subscribed.)
No need to say that, Git mailing list is sane and doesn't do reply-to munging.
> The question here then is, what remote branch should git push to - since pushremote only specifies a repo? I can suggest two options:
>
> - A: push to branch.*.merge if it's defined; otherwise push to <current branch> (like push.default=current)
> - B: push to <current branch> regardless
Or C: introduce the concept of a publish branch to complement pushremote:
http://article.gmane.org/gmane.comp.version-control.git/233572
-- 
Felipe Contreras
Previous: Junio C Hamano
Message 3 of 3 in “push.default=upstream doesn't play nicely with remote.pushdefault/branch.*.pushremote”
  1. Ximin LuoSep 10, 2013
  2. Junio C HamanoSep 10, 2013
  3. Felipe ContrerasSep 11, 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.