Since Google Code is going to be shut down we need a new place for the Vim repository. Many users have given their opinion and github appears to be the preferred site.
This is not without disadvantages, since it means moving from Mercurial to git. Some may like this, some not. Will take some getting used to. I personally prefer the Mercurial commands, they are more obvious to use. You can find help only for how a Mercurial command translates to git, e.g. https://github.com/sympy/sympy/wiki/Git-hg-rosetta-stone To see how well this works I have created a SNAPSHOT of the repository. This way we can try it out. I already verified that I can push patches there. However, for now development will remain on code.google.com. The issues were already changed after the migration, this will continue. Look here: https://github.com/vim Please respond to the list if something doesn't work well. NOTE: Before the actual migration the current repository on github will be wiped! -- TIM: Too late. ARTHUR: What? TIM: There he is! [They all turn, and see a large white RABBIT lollop a few yards out of the cave. Accompanied by terrifying chord and jarring metallic monster noise.] "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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.
