On Sun, Feb 8, 2015 at 12:54 PM, Bram Moolenaar <[email protected]> wrote: > > Eliseo wrote: > >> Hi, I'm the author of those commits. >> >> As I said to Christian, I try to send patches, or at least report, the >> important issues we find. >> I can't guarantee doing it always (for minor issues), though. For, >> frankly, as code diverges, it becomes more and more difficult to state >> if a given issue is shared, and to port corresponding changes. >> >> For these two particular commits, I hadn't taken action yet, because >> they're still under review. In fact, the second one has already been >> corrected to account for another return hidden within the POP macro. >> >> You can see current state at https://github.com/neovim/neovim/pull/1947. > > Thanks. Yeah, when the code diverges it will be difficult to fix > problems in both codebases. But it will work so long as the problem is > in common code.
In addition to what Eliseo said, we will make an effort to label relevant coverity issues, etc., with the vim-bug label. At any time, you can see all vim-bug issues via this URL: https://github.com/neovim/neovim/issues?q=label%3Abug-vim Justin M. Keyes -- -- 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/d/optout.
