Hi, I've finally written a basic script (without any error handling so far) for automatically fetching the patch files, applying, formatting the commit message and committing to the vim_extended/vim_mainline git repositories. So from now on these repositories are no longer based on the official subversion repo. Of course it still contains all the older commits in the history from svn, this is not the planned rewrite of the repository.
What do you think about the commit message format, is it ok? I searched for a git-like message, without losing information. The duplicated first line of the problem description is unavoidable I think, because it should be fully automated and the first line shouldn't merely contain the patch number. When new patches are published, I will normally update the repositories once in the evening. But if you think no, I'm too slow, that's too late, you can use the same script I'm using and comfortably fetch and apply the patches yourself. It's available in the stuff branch. Normally you wouldn't even have to worry about the updates from the repo later: if you pull, you will simply be already up to date, since the commits you created have the same SHA1s than mine. OK, this should be the desired case, but it's currently not true, the SHA1s can differ dependent on the time zone. This will be fixed, I just don't know exactly, how. Should I just assume UTC offset +0000, which is wrong? The time zone information is not included in the patch file. My current time zone is the same as Bram's :) A new branch is online: fix/fast-join It contains the patches for the improved :join algorithm from Milan Vancura. It is not yet included in the monster 'master' branch due to lack of time. I have to pack for FOSDEM, have to get up at 4 AM. Anybody else there? Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
