Hi Markus!
It's nice to see that you respond that fast! Would you mind me collecting all major vim patches which maybe will never be merged into mainline? I'd like to create top-git branches for them maybe pushing them to your repo? The vim wiki could be used to explain which branch adds which features and how stable a branch is. The idea is to make patch writers responsible to keep their patches upstream. Most of the time they do so anyway. If they don't you can clearly see which work has to be to update a patch. vim-dev list: Do you think it's ok to add a pointer on vim.org download page telling about this "vim-experimental-maybe-next" wiki page? My goal is that trying out a new feature is as easy as: git clone ... git checkout branch ./configure --enable-... make This is important to get more testers so that features become more stable. Of course I don't want to force anyone using git if they prefer bazaar. I found one use case some month ago I couldn't do in bazaar such as finding a patch adding a line or such. It was in bazaar unstable that time. I didn't find a task I couldn't do with git. That's why I most familiar with it today. Marc Weber --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
