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

possible bug when pushing with multiple remote repos.

From
AMArnaud Mouiche <arnaud.mouiche@invoxia.com>
Date
Oct 22, 2010, 09:12 UTC
Message-ID
<1287738771.13348.34.camel@amolinux>
Hi, 
I found a behavior which is, at least, different from what "git help
push" seems to declare.
basically:
- if I have 2 remotes : 'origin' and 'remote_B'
- if I checkout with tracking a branch of 'remote_B'
- if I do "git push remote" or "git push" or "git push -repo=remote_B"
then git try to push all my branches of "origin" to remote_B.
I check with latest git 1.7.3.2, and the issue is still here.
strangely:
- git checkout master
- git push  =>  this is OK, and doesn't try to push any remote_B
references to origin.

I found this is particularity error prone as origin/master can be a fast forward of remote_B/master, and in this case nobody will complains.. (that's what happened to me ;-) )

attached to this mail, a simple script that show the evidence.

regards, arnaud

Next: Santi Béjar
Message 1 of 3 in “possible bug when pushing with multiple remote repos.”
  1. Arnaud MouicheOct 22, 2010
  2. Santi BéjarOct 22, 2010
  3. Santi BéjarOct 22, 2010

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.