Excerpts from Raúl Núñez de Arenas Coronado's message of Sat Jul 18 19:35:19 +0200 2009: > For me, saving time for Bram is enough. Doesn't git solve all these problems in the nicest way possible? All those patches can be added as top-git branches. If you miss a piece you can add it later and update the following patches automatically. Updating is as much work as doing git pull.
By the way have a look at this git repo: It may already contain most of those patches. git://repo.or.cz/vim_mainline.git I think raw patches are nice. But I personally prefer git much more. (You can still use git to export those patches automatically). One implementation I like is top-git. And it would be best for vim if git was the "main" repo because working on local patches is very easy if you learned how to do it once (My experience. Yours may differ) And it's not only about Bram's time. It's a about everyone's time trying playing around with the code and new features. If you like I can write down a short introduction to top-git showing why it's a great collaborative tool to keep patches (and their merges) up to date. Marc Weber --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
