Re: Please discuss: what "git push" should do when you do not say what to push?
- From
- H. Peter Anvin <hpa@zytor.com>
- Date
- Mar 18, 2012, 04:02 UTC
- Message-ID
- <4F655E53.6030408@zytor.com>
- In-Reply-To
- <CADVrmKSGbA2gWVyPLMCBay3EikOykwq3eEH1+qWCpZvOron3Aw@mail.gmail.com>
On 03/17/2012 11:43 AM, fREW Schmidt wrote:
Show 12 quoted lines
> 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.
-hpa