Edward Fox wrote:
> Why not simply create a certain number of branches in the Subversion > repository for those semi-official patches? That'll be easier for the > end users to check out the patched code or merge the changes from > multiple branches. The patches' developers will also benefit because > we can easily use some scripts to sync your official changes from the > mainstream and keep their patches always up-to-date. A repository is only one of the things one would use for a patch. There also needs to be text that explains what it does (and where it breaks), screenshots, etc. And some people may only have a diff file. Or prefer CVS, git, etc. There is also a permission problem with everybody using the same repository. Merging with the distributed Vim source code is up to the person who created and maintains the patch. There are many ways to do this. I think that allowing every patcher to choose the method of distribution that they are comfortable with lowers the threshold to publish the patches. -- >From "know your smileys": :-)-O Smiling doctor with stethoscope /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
