From: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Date: Sun, 18 Mar 2012 05:43:43 GMT
Subject: Re: Please discuss: what "git push" should do when you do not say what to push?
Message-ID: <CAMkPkZVuW-5=o=pdfrymVkPu3k_DS1DDH_wuGXoXnq3=Z+LN_w@mail.gmail.com>
In-Reply-To: <4F655E53.6030408@zytor.com>

On Sun, Mar 18, 2012 at 12:02 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 03/17/2012 11:43 AM, fREW Schmidt wrote:
>> On Sat, Mar 17, 2012 at 12:10 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>>
>>> There is a proposal to change the default behaviour of 'git push' on the
>>> Git mailing list. The goal of this message is to encourage you to discuss
>>> it before it happens (or the change is aborted, depending on the outcome
>>> of the discussion).
>>
>> I personally much prefer the one where it pushes the current branch to
>> its tracking branch only.  That leaves very little room for surprises
>> and mistakes (the one exception being git push after git checkout -b
>> new-branch origin/master.)
>>
>
> I would agree with this being the least surprising behavior.  I believe
> this is what push.default = upstream does.
>
I agree that the least surprising default is to push the current
branch to its tracking branch only. It always surprised me that other
branches tried to push too.

Marcus