Richard Hartmann, 30.06.2008: > > On Sun, Jun 29, 2008 at 17:02, Ag. D. Hatzimanikas <[EMAIL PROTECTED]> wrote: > > > Besides that it looks like a useful option, (with this chance) I would > > like to suggest a new project, with the simple purpose to gather or to link, > > to all those patches from different sources for different purposes and > > needs, that are not *yet* on the mainline or for some reasons they will > > never be. > > This could indeed be a useful tool. A MM series for VIM, so to speak. > I would argue that seperating the the 'they will never make it' and the > 'they might make it' patchsets would make more sense, though. The > focus of the one is to be a stable VIM alternative, the other would be > a testbed of sorts.
I also was immediately reminded on the recently started linux-staging tree for drivers and similar stuff for the Linux kernel in patch form. See http://git.kernel.org/?p=linux/kernel/git/gregkh/staging.git;a=summary I don't know what's the status of the Vim patches that Ag. listed, but at least some web pages seem to be a bit outdated. Perhaps the death of those patches can be avoided with a Vim Patches Project!? Of course there need to be maintainer people. Without thinking any further, I got the idea of a "master patch", which helps in integrating the other patches into the source tree. After applying the master patch, you are able to select different patches for automatic downloading, applying, unapplying, ... Markus --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
