sponsor Vim development Vim logo Vim Book Ad

Moving from Google Code to Github

What changed?

Vim used to have a Mercurial repository on Google code. This has worked well for many years, but unfortunately the Google code site is being turned down in 2015.

Vim users on the vim-dev mailing list were asked what they thought would be the best alternative. Opinions varied, in the end GitHub was the most favorite choice.

Moving to GitHub not only means a different location, it also means switching from Mercurial to Git. But don't despair, if you want to stick with Mercurial that is possible, the instructions are below.

We are using the opportunity to clean up the repository: Remove dead branches, clean up tags, etc. This work was figured out by Markus Heidelberg.

Current status

The move is done! The Google code repository is "frozen". Do not add new issues or edit issues, these changes will be lost!

Moving over to GitHub - if you have no local changes

This is easy: Just get rid of your Mercurial repository, create a new git repository and pull from GitHub. Instructions are on this page.

Moving over to GitHub - if you have local changes

You need to export your local changes from the Mercurial repository and import them into git.

TODO (discuss this on the vim-dev maillist)

(you can create a diff and apply it to the git repository, but if you have commits these won't be taken over).

Keep using Mercurial

There is a Mercurial mirror of the GitHub repository at BitBucket. We expect it to be reliable, but it's a mirror, thus there is an extra point of failure.

To switch to the new Mercurial repository, simply edit the file .hg/hgrc in the Mercurial vim repository and change the following line

[paths]
default = https://code.google.com/p/vim/
to the new repository:
[paths]
default = https://bitbucket.org/vim-mirror/vim
That's it. Run hg pull -u to fetch from the new Mercurial repository and update your working copy.

For developing patches, you can proceed as mentioned at the Mercurial page



If you have questions or remarks about this site, visit the vimonline development pages. Please use this site responsibly.
Questions about Vim should go to the maillist. Help Bram help Uganda.
   
OSDN.net Logo