On Mo, 24 Aug 2015, Marvin Renich wrote: (I have set up an forwarding of all notifications from the vim repository to the vim-dev ml).
> I have started getting mail from "Vim Github Repository"; apparently > they are pull-requests forwarded to vim-dev. I have two problems with > this mail. First, the person who sent the PR isn't identified. (This > was also a problem with the Vim problem tracker.) > > Second, the List-ID headers are different, depending, I think, on the > repository where the PR originated. Here is a sample: > > List-ID: dyng/ctrlsf.vim <ctrlsf.vim.dyng.github.com> I apologize, I did cause this by not being careful enough. That happened, when commenting on an issue, while still being logged in as the vim-ml user. That shouldn't happen anymore. Ideally, I shouldn't need to log in as that user anymore. > I think the fact that vim occurs at all in the list-id is purely > coincidental based on the fact that the repo name contains vim. That comes from the notification mails from github. > The list-id should be constant and based on the list to which I am > subscribed, not the list where the message originated. One of the major > purposes of the list-id and related headers, such as list-unsubscribe, > is so that the recipient can identify why he/she is receiving the email > and do something about it if the emails are unwanted (either because > someone else subscribed him or he is no longer interested). > > Another purpose, which is more important to me at the moment, is that > the list-id allows sorting incoming mail (at delivery time for some of > us). I am not going to start rewriting mails, that are sent from github. It's just a simple forwarding, since the original github notification mail is rejected by the google groups page. (I tried to add the reply address into the reply-to, so that replies also end up at the issue tracker, but apparently, google groups clears this header completely before adding the googlegroups address.)[1] > Also, vim-dev has a lot of discussion that is not directly related to > PRs. I think it would be nice for the PRs to go to a separate list, > such as vim-repo or vim-source. Many people who are currently > subscribed to vim-dev will want to subscribe to the new list, but not > all. Having the PRs separated from general development discussion would > be a benefit. This could be discussed. I actually think, it is nice that issues can be discussed on this list and also we should see how much additional traffic will be created by the issue tracker. However you could filter the Header List-ID: vim/vim <vim.vim.github.com> to a different folder. [1] Currently there is a X-Github-Reply-To Header, which contains the reply address for github. So if replying to that address the message should show up at github. Best, Christian -- Was die neuen Unwissenden holen müssen: Tankinnenbeleuchtung -- -- 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.
