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

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

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Mar 31, 2010, 15:14 UTC
Message-ID
<vpq1vf0a5gs.fsf@bauges.imag.fr>
In-Reply-To
<h2x530ac78e1003310754v88853e2bj6d59d835025ec140@mail.gmail.com>
Phil Lawrence <prlawrence@gmail.com> writes:
Show 6 quoted lines
> 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/
Previous: Phil LawrenceNext: Phil Lawrence
Message 2 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.