Possible change to the "git push" behavior

[Martin Geisler]

Greg Ward <greg at gerg.ca> writes:

> On 20 March 2012, Angel Ezquerra Moreu said:
>> It seems that the Git project is considering changing the default
>> behavior for the "git push" command (http://lwn.net/Articles/487131).
>> 
>> Since mercurial bookmarks are meant (AFAIK) to behave similarly to git
>> branches, would mercurial change the way bookmarks work if git changes
>> the way git branches work? How would that work given mercurial's
>> backwards compatibility policy?
>
> I don't speak for Matt or for anyone else, but I suspect the answer is
> "not bloody likely". "hg update" does not behave the same way as "cvs
> update" does, so why should "hg push" behave the same way as "git
> push"? Mercurial is its own project with its own aims and its own
> policies.
>
> That said, the "push all changesets by default" policy could be a
> minor annoyance when using bookmarks.

I know this is about bookmarks, but as a related data point, I can
mention that Henrik and Sune's repoman wrapper always operates with a -b
flag in order to push/pull the right named branch instead of operating
on all of them.

Last time I spoke with them about it, they said that it would be
impossible (very impractical) for them to push/pull everything by
default.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://www.aragost.com/mercurial/