On Jun 3, 2013 7:42 PM, "Bram Moolenaar" <[email protected]> wrote: > > > Ben Fritz wrote: > > > On Monday, June 3, 2013 4:16:12 AM UTC-5, Bram Moolenaar wrote: > > > ZyX wrote: > > > > > > > On Jun 3, 2013 1:09 AM, "Bram Moolenaar" <[email protected]> wrote: > > > > > > > > Glts wrote: > > > > > > > > > On Sunday, June 2, 2013 9:30:20 PM UTC+2, Bram Moolenaar wrote: > > > > > > > > > > Christian Brabandt wrote: > > > > [...] > > > > And there are no PR's here. Other issue tracker problems are tolerable, > > > > absence of PR's and attachments makes it impossible to hold patches there > > > > making it useless when it comes to resolving the mentioned problem. > > > > > > What's a PR? Problem Report? > > > > I think he is referring to a "pull request", so that somebody can fix > > an issue in a clone of the repository, and request that you pull in > > and merge the changes. > > > > I didn't get the impression that was something you'd want to do anyway. > > > > But maybe you'd start accepting Hg "bundle"s? Then there would be no > > doubt where the changes were based on and less bitrot compared to a > > patch (though a merge or rebase will be needed). > > Context diffs work just fine. Anybody with basic Linux tools can use > them, no need to figure out hg or git commands and setting up an > environment where they work. I hardly ever had a problem with "bitrot", > except for refactorings where nothing would help. > > [...] > > > 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. > > There was a promise from someone to keep the Issue Tracker up to date, > close fixed issues and so on, but that doesn't really appear to happen. > I don't really have time to do that on top of everything else.
The basic idea of having an issue tracker is that *all* bugs, feature requests and pull requests (PR's) go there. Thus you don't need to sync anything since there is nothing to sync with. I.e. switching to issue tracker means shutting down vim-dev mailing list. Otherwise it is not that useful and it either needs to be kept in sync or will contain only partial information. Note that even Google code bug tracker allows using regular emails to respond to the issue. > In an ideal world everything happens wonderfully, we'll have to live > with the real world. > > -- > hundred-and-one symptoms of being an internet addict: > 68. Your cat always puts viruses on your dogs homepage > > /// 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.
