From: Arnaud Mouiche <arnaud.mouiche@invoxia.com>
To: git@vger.kernel.org
Subject: possible bug when pushing with multiple remote repos.
Date: Fri, 22 Oct 2010 11:12:51 +0200 [thread overview]
Message-ID: <1287738771.13348.34.camel@amolinux> (raw)
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
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
[-- Attachment #2: test.sh --]
[-- Type: application/x-shellscript, Size: 2199 bytes --]
next reply other threads:[~2010-10-22 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:12 Arnaud Mouiche [this message]
2010-10-22 9:32 ` possible bug when pushing with multiple remote repos Santi Béjar
2010-10-22 9:36 ` Santi Béjar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1287738771.13348.34.camel@amolinux \
--to=arnaud.mouiche@invoxia.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).