Re: git push (mis ?)behavior

From: Wincent Colaiuta <win@wincent.com>
Date: Oct 3, 2007, 06:47 UTC
Message-ID: <0F838789-B02F-4081-8C75-ED06B551D4C0@wincent.com>
In-Reply-To: <buoprzwn5qm.fsf@dhapc248.dev.necel.com>

El 3/10/2007, a las 7:10, Miles Bader escribió:

Show 15 quoted lines

> Junio C Hamano <gitster@pobox.com> 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)

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.