git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git push doesn't honor .git/config

From
Phil Lawrence <prlawrence@gmail.com>
Date
Mar 31, 2010, 22:03 UTC
Message-ID
<w2u530ac78e1003311503m3a70b571ge9708428911f6582@mail.gmail.com>
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:

Show 15 quoted lines
> 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
Previous: Matthieu Moy
Message 3 of 3 in “git push doesn't honor .git/config”
  1. Phil LawrenceMar 31, 2010
  2. Matthieu MoyMar 31, 2010
  3. Phil LawrenceMar 31, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.