Re: git push default behaviour?
- From
- Jeremy Morton <jeremy@configit.com>
- Date
- Mar 8, 2012, 10:43 UTC
- Message-ID
- <CAFsnPqpoBLHoshgv0MsUUStA3Q=niM8hP9yaHr+rSQvh-JWHZA@mail.gmail.com>
- In-Reply-To
- <1331203321.21444.13.camel@beez.lab.cmartin.tk>
Obviously - but my point is that it needn't be so dangerous by default. It tries to push all matching branches - is that really a more common requirement than pushing the current branch?
Best regards, Jeremy Morton (Jez)
On Thu, Mar 8, 2012 at 10:42 AM, Carlos Martín Nieto <cmn@elego.de> wrote:
Show 12 quoted lines
> On Thu, 2012-03-08 at 10:38 +0000, Jeremy Morton wrote: >> 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. > > Then don't use --force without specifying exactly what you want. > Anything with that option needs to be used carefully. > > cmn > >