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

Re: git push (mis ?)behavior

From: Wincent Colaiuta <hidden>
Date: 2016-06-15 22:43:38

El 3/10/2007, a las 7:10, Miles Bader escribió:
Junio C Hamano [off-list ref] writes:
quoted
I think it is sensible to have an option to make it push only the
current branch.  I am not sure if it is sensible to make that the
default.
I really like the current default, it matches my mental model well:  I
generally use "push" to mean "synchronize the remote repository  
with my
current one"; if multiple branches have changed, I want those changes
propagated too.

I think changing it would be a bad idea, it just seems a pointlessly
incompatible change.  The reasons I've seen offered on this thread for
changing the default seem pretty weak, e.g., "it's more conservative"
(but more annoying)
It could be more annoying for some, yet a life saver for others. So  
before changing the default obviously we would need to get a clear  
idea of whether or not the majority would approve of such a move.  
Such differences of opinion would be easily accommodated if the  
default behaviour were made configurable. That way everyone can have  
the behaviour they want.

Cheers,
Wincent

PS. I'm the one who mentioned SVK, but I didn't offer it as a reason  
to justify the change (I agree, more than "weak" it's not really any  
reason at all); I  just mentioned to indicate why it is that the  
current behaviour caught me off guard.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help