Junio C Hamano [off-list ref] writes:
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?).
-Miles
--
Freedom's just another word, for nothing left to lose --Janis Joplin
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.
On Wed, Oct 03, 2007 at 05:10:09AM +0000, Miles Bader wrote:
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 understand that … and I know some people rely on the current
behavior…
I think changing it would be a bad idea, it just seems a pointlessly
incompatible change.
There definitely is a point: with the current behaviour you sometimes
end up pushing more than what you meant, with sometimes WIP that you
intend to rebase, and it hurts. Git porcelains should help you avoid to
shoot yourself in the foot, hence I think that (especially to git
newcomers), the current default _is_ dangerous.
Though, OTOH, I believe that git push <remote> could keep the current
behavior. I'm also okay with the fact that git push could be
configurable in that regard.
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org