Sorry for the duplicate, Bram. I meant to include the list and forgot to "reply all".
On Mon, Jun 3, 2013 at 10:42 AM, Bram Moolenaar <[email protected]> wrote: > > Ben Fritz wrote: > >> One problem with the todo list, is that it is not up-to-date until you >> publish runtime files periodically. So sometimes it is hard to tell >> whether you noticed a patch or fixed a bug in a later version. And, >> once a bug goes away from the TODO list, nobody can find it later to >> see that it was an issue but has been fixed (and when). > > Keeping the TODO list up-to-date is less work than updating stuff on > some website. Whatever issue tracker there is, it's not going to make > MY work more efficient. And since I'm the bottleneck that's what > matters. > I assume you keep the todo list up-to-date as you work, but you just don't commit/push it until you have other runtime file updates to push. Do you think you could commit/push the TODO list alongside the patch (or patch series) when you apply it? That might help to some extent. Looking at the patches README can help figure out when/if something got fixed. But it is still sometimes hard to figure out from the short patch description, what the specific issue is. An issue tracker ID is helpful there, but a vim_dev discussion link might do as well. Or at least a date to go with the name of the person reporting/fixing it. List admins (or any other responders on the list) can help with having too many different discussions on the same issue, by referring any duplicate discussions back to the first discussion and continuing there only. There is a "close topic" action admins can apply to any thread, I assume this will prevent new posts to a topic if it has been referred to a different thread. -- -- 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.
