On Tue, Jan 20, 2009 at 5:39 PM, Milan Vancura <mi...@ucw.cz> wrote: > >> 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? >
alternatively, if pushing and creating branches creates more work for Markus, you can send directly bundles of your own branches/experiments to him. please have a look at http://www.kernel.org/pub/software/scm/git/docs/git-bundle.html. sending a git-bundle to a repo maintainer is actually better than sending patches. my 2 cents :) -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside ! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
