News for hackers. Stuff that matters.
Re:Vim is moving to GitHub by guelo on Wednesday March 25, 2015 @11:53AM (#9263729)
Why would the source of the remote make a difference for fetching from an upstream?
Re:Vim is moving to GitHub by mackwic on Wednesday March 25, 2015 @12:05PM (#9263819)
Technically, it doesn't. In practice, using a unified and polished interface like Github make things easier.
Re:Vim is moving to GitHub by Crito on Wednesday March 25, 2015 @02:21PM (#9264881)
I feel like actually creating a fork of vim that is viable for the community is a much higher bar. If that first bar stops somebody, is it likely that they would have cleared the second bar?
Re:Vim is moving to GitHub by samspot on Wednesday March 25, 2015 @12:07PM (#9263831)
Vim appears to be Mercurial while Neovim is Git. I imagine merging is a lot easier when you are on the same VCS :)
Re:Vim is moving to GitHub by michaelmior on Wednesday March 25, 2015 @02:54PM (#9265114)
You can use hg-git[0] to push to Git from a Mercurial repository. Then it's basically just like working with another Git repository. It does mean that you need some way of mirroring the two. I've never tried it, but it looks like you can use git-hg[1] to use a Mercurial repository like a regular Git remote.

[0] https://hg-git.github.io/ [1] https://github.com/cosmin/git-hg

Re:Vim is moving to GitHub by sigzero on Thursday March 26, 2015 @09:25AM (#9269341)
I don't think there is going to be a lot of merging behind done so it probably doesn't matter.