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.
On 2008-09-20, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > There are several patches available for Vim. Some are mature, some > unfinished. > > Until now there was no central place that lists these patches, like we > have for Scripts. Adding patches to the scripts database doesn't look > right. > > So I created a page that can be edited: > http://groups.google.com/group/vim_dev/web/vim-patches > > I have added the 2008 Google Summer of Code entries as an example. > If you want people to know your Vim patch, please add it here! > > This should be an overview, with links to where more information can be > found. Add just enough information for people to know if this is an > interesting patch for them. > > To make the page editable I had to enable adding and editing pages for > group members. That probably means we will get some spam. Please > remove it when you see it. > > -- > How many light bulbs does it take to change a person? > > /// 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 /// > > > > -- Sent from Gmail for mobile | mobile.google.com --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
