Xavier de Gaye wrote: > On Sun, May 26, 2013 at 7:12 PM, Bram Moolenaar wrote: > > > > ZyX wrote: > > > >> This is the last huge hunk I can write before the end of May. Other > >> parts of RFC are to be delayed. > > > > Thanks for all your work! > > > > I have a few more patches for Python listed, hopefully I can include > > them all this week. > > > The author of "[PATCH] (1/?) Fix “invalid read” valgrind errors" has > admitted that this patch is not correct, so it should not be included. > > "[PATCH] (15/?) More possible memory leak fixes and error checking" > creates the new macro DICTKEY_CHECK_EMPTY that is removed afterwards > by "[PATCH] (28/?) Remove some possible memory leaks", so patch 15 > should not be included as well.
Thanks for your remarks. Not including some patches may cause merge conflicts for what follows. It might be easier to just include them in sequence. ZyX - perhaps you can make a sequence of "fixed" patches? I suppose that's not so easy, once committed you need another commit to fix something. Perhaps someone can try out what happens when not including the 1/? and 15/? patches? -- hundred-and-one symptoms of being an internet addict: 5. You find yourself brainstorming for new subjects to search. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
