From: Phil Lawrence <prlawrence@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git <git@vger.kernel.org>
Subject: Re: git push doesn't honor .git/config
Date: Wed, 31 Mar 2010 17:03:22 -0500 [thread overview]
Message-ID: <w2u530ac78e1003311503m3a70b571ge9708428911f6582@mail.gmail.com> (raw)
In-Reply-To: <vpq1vf0a5gs.fsf@bauges.imag.fr>
On Wed, Mar 31, 2010 at 10:14 AM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Phil Lawrence <prlawrence@gmail.com> writes:
>> ...
>> 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.
Thank you! That was helpful.
Phil Lawrence
prev parent reply other threads:[~2010-03-31 22:03 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
2010-03-31 22:03 ` Phil Lawrence [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=w2u530ac78e1003311503m3a70b571ge9708428911f6582@mail.gmail.com \
--to=prlawrence@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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).