Possible change to the "git push" behavior
Greg Ward
greg at gerg.ca
Tue Mar 20 08:01:40 CDT 2012
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've pondered ways to improve
things that don't break compatbility or seem insane, but have not
thought of anything so far. I certainly haven't looked to git for
inspiration, because I always feel like a total newbie when I use git.
(And that's with, what, 3+ years of occasional experience. I've
actually been using git for longer than I've been using hg, and I
still feel like a newbie.)
Greg
--
Greg Ward http://www.gerg.ca/
"Question authority!" "Oh yeah? Says who?"
More information about the Mercurial-devel
mailing list