From: Felipe Contreras <felipe.contreras@gmail.com>
To: Christophe <Christophe.Troestler@umons.ac.be>, git@vger.kernel.org
Subject: RE: git-remote-hg
Date: Sat, 12 Apr 2014 16:42:35 -0500 [thread overview]
Message-ID: <5349b34bb72db_473d1391308ac@nysa.notmuch> (raw)
In-Reply-To: <20140120.181832.898588286941108442.Christophe.Troestler@umons.ac.be>
Christophe wrote:
> I am using git-remote-hg to access to projects on bitbucket. I can clone the
> master branch fine and push to it. I also see hg branches as
> remotes/origin/branches/«branch». However, if I create a local branch
> "branches/x" and want to push it to remotes/origin/branches/x, it gets pushed
> to the remote master (aka default) branch.
Which version of the script and Git are you using?
If I do `git push origin branches/test` it works fine, I can see the branch in
bitbucket.
> What is the recommended way of working with multiple branches when
> interacting with a remote hg repository?
My recommendation is to avoid them (I don't see the point of them), but they
should work.
--
Felipe Contreras
prev parent reply other threads:[~2014-04-12 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 17:18 git-remote-hg Christophe
2014-04-12 21:42 ` Felipe Contreras [this message]
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=5349b34bb72db_473d1391308ac@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=Christophe.Troestler@umons.ac.be \
--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).