From: Leandro Lucarella <leandro.lucarella@sociomantic.com>
To: git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: branch.<name>.pushremote not working with push.default simple or upstream
Date: Fri, 7 Jun 2013 14:41:47 +0200 [thread overview]
Message-ID: <20130607124146.GF28668@sociomantic.com> (raw)
Hi, I tried to use the new Git feature to push by default to a different
remote you normally pull but I had some problems. I asked in the #git
IRC channel and been told it looks like a bug and to report it here.
I have 2 remotes, origin and upstream. origin is my private fork (and I
can push to it) while upstream is read-only for me. I have only one
branch, 'master' (present in all the remotes), originally tracking
origin/master.
I changed branch.master.remote to upstream and set
branch.master.pushremote to origin, but when I do I git push I get an
error:
$ git push --dry-run --verbose
fatal: You are pushing to remote 'origin', which is not the upstream of
your current branch 'master', without telling me what to push
to update which remote branch.
I'm using push.default 'simple' to stay forward compatible with Git 2.0.
In the IRC channel they suggested to try with other push.default
settings and I did. 'matching' and 'current' works, but 'simple' and
'upstream' fail with the error message above.
Thank you.
--
Leandro Lucarella
Senior R&D Developer
sociomantic labs GmbH <http://www.sociomantic.com>
next reply other threads:[~2013-06-07 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 12:41 Leandro Lucarella [this message]
2013-06-07 14:11 ` branch.<name>.pushremote not working with push.default simple or upstream Ramkumar Ramachandra
2013-06-07 15:47 ` Junio C Hamano
2013-06-07 16:14 ` Leandro Lucarella
2013-06-07 16:57 ` Ramkumar Ramachandra
2013-06-07 17:07 ` Leandro Lucarella
2013-06-07 17:33 ` Ramkumar Ramachandra
2013-06-07 16:51 ` Ramkumar Ramachandra
2013-06-07 18:34 ` Junio C Hamano
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=20130607124146.GF28668@sociomantic.com \
--to=leandro.lucarella@sociomantic.com \
--cc=artagnon@gmail.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).