On Friday, March 27, 2015 at 4:06:47 PM UTC-5, Bruno Sutic wrote:
> - lastly, it has been mentioned a couple times vim plugin community is
> already on github. The objective statement that proves this: github
> currently has 42,636 vim related repositories, bitbucket has only 1652
> (this is based on a simple search for "vim" on both github and
> bitbucket).

Does this "simple search" include the automatically created mirrors that
Vundle created for each and every vim.org plugin? Authors that have no
presence on Github whatsoever nevertheless have their plugin on github
due to this.

Does it count the individual forks? How about private forks? On GitHub,
IIUC, you cannot create a private fork of a public repository. I think
this is quite possible on BitBucket. Would these show up in a search?

And I know gundo and probably a few other plugins have a github
presence...but also a BitBucket presence. Which is their "primary", if
they even have a primary, I have no idea.

Even if these numbers are accurate, your arguments basically boil down
to "Git is popular. Let's do the popular thing and move to Git."

Now that I've proven myself a curmudgeon (thanks, Manuel :-)), I present
only reason beyond current fashion trends I can think of why it makes
sense to move to git:

Bram does his own thing when you send him a patch. He has even said pull
requests will probably become patches in his new workflow. Mercurial is
designed to keep all data, always. git is designed to forget data when
it's not needed anymore. So when Bram commits a patch, you can easily
tell git to forget the changesets that led up to that patch. It's harder
with Mercurial (though not impossible, using "evolve" or "strip" or
similar).

Maybe none of this matters. Bram, have you definitely decided you're
taking Vim to GitHub? Do we all just need to shut up and accept it?

-- 
-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui