From: dexen deVries <dexen.devries@gmail.com>
To: git@vger.kernel.org
Subject: push from git gui goes to wrong branch
Date: Mon, 20 Dec 2010 15:09:22 +0100 [thread overview]
Message-ID: <201012201509.22236.dexen.devries@gmail.com> (raw)
Hello,
there's a behavior in git gui (v1.7.3.2 and previous) that I consider bugous.
Failed to find any bugreporting system on git's website so I'm reporting it
here; please correct me if that's wrong.
I have the following snippet in my .git/config:
[branch "article"]
remote = baron
merge = refs/heads/dexen-article
However, the `Push' button from git gui sends local branch `article' to remote
branch `article', rather than to the indicated `dexen-article'.
For reference, with the CLI `git push', the local branch `article' is pushed
to remote branch `dexen-article' as expected.
Regards,
--
dexen deVries
``You want to make your way in the CS field? Simple. Calculate rough time of
amnesia (hell, 10 years is plenty, probably 10 months is plenty), go to the
dusty archives, dig out something fun, and go for it. It's worked for many
people, and it can work for you.'' - Ron Minnich
reply other threads:[~2010-12-20 14:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201012201509.22236.dexen.devries@gmail.com \
--to=dexen.devries@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).