Thread (15 messages) flat view 15 messages, 8 authors, 2016-06-15

Re: git push default behaviour?

From: Jeremy Morton <hidden>
Date: 2016-06-15 22:53:15

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 [off-list ref] wrote:
On Thu, 2012-03-08 at 10:38 +0000, Jeremy Morton wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help