From: Jeremy Morton <jeremy@configit.com>
Date: Thu, 08 Mar 2012 10:38:15 GMT
Subject: Re: git push default behaviour?
Message-ID: <CAFsnPqpnH2CTki8zz6Mpz=qrdxF_aTA92cPrn1L9MQZVMoxdeg@mail.gmail.com>
In-Reply-To: <1331202483.21444.11.camel@beez.lab.cmartin.tk>

But 'push --force' WILL try to push your (probably outdated) master
upstream, killing any changes there made since you last updated.  That
alone is so dangerous it seems like reason enough to avoid it by
default.

Best regards,
Jeremy Morton (Jez)

On Thu, Mar 8, 2012 at 10:28 AM, Carlos Martín Nieto <cmn@elego.de> wrote:
> On Thu, 2012-03-08 at 10:13 +0000, Jeremy Morton wrote:
>> Right, so I guess I'm saying that the default value for push.default
>> should be upstream instead of matching...
>
> Any default is going to leave some people unhappy. If upstream is the
> right thing for you, then that's what you should use. Most questions I
> see about push not doing what the users expect would actually benefit
> from 'current'. 'matching' is a fairly safe default, as it won't try to
> push private branches or changes in private branches that track
> something upstream.
>
>   cmn
>
>