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

Phil Lawrence [off-list ref] 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/

On Wed, Mar 31, 2010 at 10:14 AM, Matthieu Moy
[off-list ref] wrote:

Phil Lawrence [off-list ref] writes:

quoted

...
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