On 4/16/2015 1:33 PM, Nikolay Pavlov wrote:
More powerful?! Try to add phases/changeset obsolescense/branches/etc to git.
The point is that this “sharper knife” has an architecture that
prevents adding feature to the core. You can do almost anything with
the core using plugins for mercurial, but maximum thing you can do
with git
There's an interesting article I ran into earlier today from facebook
develop
https://code.facebook.com/posts/218678814984400/scaling-mercurial-at-facebook/
about how they switched from git to mercurial because they needed to
work on their source control system to better scale. Bottom line
Our engineers were comfortable with Git and we preferred to stay
with a familiar tool, so we took a long, hard look at improving it
to work at scale. After much deliberation, we concluded that Git's
internals would be difficult to work with for an ambitious scaling
project.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
