> I suggest you email the list with the full patch, asking to be included in > vim_extended -- that way, you get more testing for your patch & will be able > to polish it even more if needed.
Hello Richard, I already posted all four patches to vim-dev list in two e-mails at January, 7. http://groups.google.com/group/vim_dev/tree/browse_frm/month/2009-01/c1bddee22f77a319?rnum=41&_done=%2Fgroup%2Fvim_dev%2Fbrowse_frm%2Fmonth%2F2009-01%3F#doc_9bb193025c6345df is the link to the archive pointing exactly to two e-mails of mine containing all four patches. It would be nice to have a public branch at vim_extended. (I have that branch in my local git tree cloned from vim_extended, of course. So I can push it back if having rights.) Markus, can you create such branch or contact me, please? Bram, could I ask you what is the current status of the patch set on your side? In a queue? Thank you all, Milan -- Milan Vancura, Prague, Czech Republic, Europe --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
