Thread (1 message) 1 message, 1 author, 2016-06-15

Re: git push (mis ?)behavior

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:38

Miles Bader [off-list ref] writes:
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), and "it's more like SVK" (who cares?).
Usually we hear people complain louder on the list.

People who are happy with the existing behaviour tend to be
quiet, and we should be really careful not to break things for
silent majority.

I try to stay fairly conservative, often more conservative than
what I would like to be myself, for this exact reason.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help