# git push doesn't honor .git/config

3 messages from 2010-03-31 to 2010-03-31. Participants: Phil Lawrence, Matthieu Moy.
Thread: https://gitlist.dev/t/23272

## Phil Lawrence, 2010-03-31 14:54

Subject: git push doesn't honor .git/config
Message-ID: <h2x530ac78e1003310754v88853e2bj6d59d835025ec140@mail.gmail.com>
URL: https://gitlist.dev/e/h2x530ac78e1003310754v88853e2bj6d59d835025ec140%40mail.gmail.com

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

(MIS-59_project)$ git branch -v
  MIS-38_labor_cat    cab4fe6 [MIS-38] Create Master Labor Category import SQL
  MIS-39_org          02f9e2f [MIS-39] Create Unanet's Organization export SQL
  MIS-40_approval_grp 7c3b5ec [MIS-40] Create Unanet Approval Groups import SQL
  MIS-41_location     8bd55ab [MIS-41] Create Unanet Master Locations import SQL
  MIS-42_person       9fb1901 [MIS-42] Create SQL for Unanet's Person import
* MIS-59_project      ed3acc9 [ahead 1] [MIS-59] Switch to using
get_project_type_unanet()
  MIS-65_task         651a05b [MIS-65] Switch to using get_project_type_unanet()
  master              e98c105 Retired OTL
(MIS-59_project)$ grep -A2 MIS-59_project .git/config
[branch "MIS-59_project"]
        remote = origin
        merge = refs/heads/MIS-59
(MIS-59_project)$ git push
Everything up-to-date
(MIS-59_project)$ git branch -v
  MIS-38_labor_cat    cab4fe6 [MIS-38] Create Master Labor Category import SQL
  MIS-39_org          02f9e2f [MIS-39] Create Unanet's Organization export SQL
  MIS-40_approval_grp 7c3b5ec [MIS-40] Create Unanet Approval Groups import SQL
  MIS-41_location     8bd55ab [MIS-41] Create Unanet Master Locations import SQL
  MIS-42_person       9fb1901 [MIS-42] Create SQL for Unanet's Person import
* MIS-59_project      ed3acc9 [ahead 1] [MIS-59] Switch to using
get_project_type_unanet()
  MIS-65_task         651a05b [MIS-65] Switch to using get_project_type_unanet()
  master              e98c105 Retired OTL
(MIS-59_project)$ git push origin MIS-59_project:MIS-59
Counting objects: 11, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (6/6), 498 bytes, done.
Total 6 (delta 2), reused 0 (delta 0)
=> Syncing Gitorious... [OK]
To git@gitorious.burnsmcd.com:~plawrence/mis/plawrences-ora-apps.git
   1fbf2e0..ed3acc9  MIS-59_project -> MIS-59
(MIS-59_project)$

Did I miss something, or is this incorrect behavior?  BTW, I'm running
msysgit 1.7.0.2-preview20100309 on Windows XP.

Thanks,
Phil Lawrence

```

## Matthieu Moy, 2010-03-31 15:14

Subject: Re: git push doesn't honor .git/config
Message-ID: <vpq1vf0a5gs.fsf@bauges.imag.fr>
URL: https://gitlist.dev/e/vpq1vf0a5gs.fsf%40bauges.imag.fr
In-Reply-To: <h2x530ac78e1003310754v88853e2bj6d59d835025ec140@mail.gmail.com>

```
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/

```

## Phil Lawrence, 2010-03-31 22:03

Subject: Re: git push doesn't honor .git/config
Message-ID: <w2u530ac78e1003311503m3a70b571ge9708428911f6582@mail.gmail.com>
URL: https://gitlist.dev/e/w2u530ac78e1003311503m3a70b571ge9708428911f6582%40mail.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:
> 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

```