From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Phil Lawrence <prlawrence@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git push doesn't honor .git/config
Date: Wed, 31 Mar 2010 17:14:27 +0200 [thread overview]
Message-ID: <vpq1vf0a5gs.fsf@bauges.imag.fr> (raw)
In-Reply-To: <h2x530ac78e1003310754v88853e2bj6d59d835025ec140@mail.gmail.com> (Phil Lawrence's message of "Wed\, 31 Mar 2010 09\:54\:28 -0500")
Phil Lawrence <prlawrence@gmail.com> writes:
> I renamed a local branch from MIS-59 to MIS-59_project, and did the following:
> git branch --set-upstream MIS-59_project origin/MIS-59
> git push --set-upstream origin MIS-59_project:MIS-59
>
> However, .git/config is not being honored by git push; I have to
> supply all the parameters to actually push changes.
... or read the man better ;-)
branch.<name>.merge
[...] It tells git-fetch/git-pull which branch to merge and
can also affect git-push (see push.default). [...]
push.default
[...]
· matching push all matching branches. [...] This is the default.
· tracking push the current branch to its upstream branch.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-03-31 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 14:54 git push doesn't honor .git/config Phil Lawrence
2010-03-31 15:14 ` Matthieu Moy [this message]
2010-03-31 22:03 ` Phil Lawrence
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=vpq1vf0a5gs.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=prlawrence@gmail.com \
/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).