> I don't think Bram can migrating to git. We had tried to persuade him > to switch to svn but he refused. I just suggest you using svk. It can > make your current situation better. > > By the way, some files within the version control will be modified if > you compile Vim in your local working directory. They are always a > major trouble to me. Many developers complained for many times, trying > to persuade Bram to remove those files out of the version control > system, but they did no help at all. That it.
I'm not saying vim should use git. The linked article describes how you can build a local git repo from an existing svn repo, how to sync it to svn updates every now and then, and how to use the git repo to create patches that you can email to this list. It doesn't require any changes for Bram (there's a svn repository already), it's just something that might be useful to other people. I'm sure you can tell git to ignore config.h and friends when generating patches too. Nico --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
