Re: Mail from Vim Github Repository
On Mo, 24 Aug 2015, Alejandro Exojo wrote: El Monday 24 August 2015, Christian Brabandt escribió: 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. Note that the sender name is lost as well. It's difficult to read who said what, so one would want to click on the link and read it on the web anyway. That should be fixed now. The authors name should be still in the from along with '(Vim Github Repository). Also I added an Mail-Followup-To header, so depending on the reply method you use, a reply might end up at github as well (which needs to be tested). Best, Christian -- Wo ich aufhören muss, sittlich zu sein, habe ich keine Gewalt mehr. -- Goethe, Maximen und Reflektionen, Nr. 141 -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
Am 2015-08-27 06:35, schrieb LCD 47: On 26 August 2015, Christian Brabandt cbli...@256bit.org wrote: [...] Also I added an Mail-Followup-To header, so depending on the reply method you use, a reply might end up at github as well (which needs to be tested). [...] Does Outlook pay attention to Mail-Followup-To these days? Does any recent mail client other than Mutt (and the now defunct Thunderbird) do it? I don't think Outlook is used in such a technical list a lot, but I honestly do not know. And while thinking about it, I suppose it does not matter, because I expect github to drop those mails, at least if they come from an address that has no github account associated with it. Also currently there is another issue, that the vim-ml account does not seem to get all notifications, although watching the repository. Best, Christian -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
On 26 August 2015, Christian Brabandt cbli...@256bit.org wrote: [...] Also I added an Mail-Followup-To header, so depending on the reply method you use, a reply might end up at github as well (which needs to be tested). [...] Does Outlook pay attention to Mail-Followup-To these days? Does any recent mail client other than Mutt (and the now defunct Thunderbird) do it? /lcd -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
On Di, 25 Aug 2015, tux. wrote: Yes, the newest patch is tagged on Bitbucket, but I don't get it :/ Did you run hg pull -u? BTW: What is this? To: Christian Brabandt vim_dev@googlegroups.com Best, Christian -- Der Religion ist nur das Heilige wahr, der Philosophie nur das Wahre heilig. -- Ludwig Feuerbach -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
Christian Brabandt schrob am Dienstag, 25. August 2015 um 19:26 Zeit: Did you run hg pull -u? Yes, but it did not change a thing. -- However, I (seem to) have found my mistake: I had local changes, mostly leftovers from the old repository. Thanks, I seem to have the right versions now. BTW: What is this? To: Christian Brabandt vim_dev@googlegroups.com My mail client's default setting. :-) Regards. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
On 2015-08-25, tux. wrote: BTW: Having my local hg repository set to Bitbucket and typing hg pull does *not* pull the newest tags, it's still at 7.4.826 for me :/ I just did that (2015-08-25 17:03Z) and retrieved through 7.4.836. vim/.hg/hgrc: default = https://bitbucket.org/vim-mirror/vim Regards, Gary -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
BTW: Having my local hg repository set to Bitbucket and typing hg pull does *not* pull the newest tags, it's still at 7.4.826 for me :/ -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
Am 2015-08-25 04:06, schrieb Marvin Renich: * Christian Brabandt cbli...@256bit.org [150824 16:28]: 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.) Any chance this can be fixed? Is this how github works for all projects that it hosts? If so, I won't bother considering github for any of my projects unless they fix this (and I would have voiced my opinion before Vim switched if I had known). I could leave the from header alone. This was done to make sure, that the mails show up in googlegroups, because the normal github mails have been blocked and I suspected sending with varying from headers (which contains the github username) will cause the mails to end up in the moderation queue. I could however change it and see if this works. Otherwise, I'll check how to get the from header into mail body as attribution. conclusion that the list-id depended on the user who sent the PR. Does that mean that in the future, all of these notifications will have list-id vim.vim.github.com? Yes, if github doesn't change anything. Best, Christian -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Mail from Vim Github Repository
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 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. 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). 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. ...Marvin -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
* Christian Brabandt cbli...@256bit.org [150824 16:28]: 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.) Any chance this can be fixed? Is this how github works for all projects that it hosts? If so, I won't bother considering github for any of my projects unless they fix this (and I would have voiced my opinion before Vim switched if I had known). 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. No problem. I saw three different List-ID's and jumped to the conclusion that the list-id depended on the user who sent the PR. Does that mean that in the future, all of these notifications will have list-id vim.vim.github.com? I am not going to start rewriting mails, that are sent from github. It's just a simple forwarding, Understandable. 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. 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. If there are not too many PRs, that will be fine. If the number of PRs gets large, a separate read-only mailing list (only the PR notifications are posted, discussion referencing the PRs still happens on vim-dev) should be considered. [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. Actually, I found X-Github-Recipient-Address after sending my email. That is what I am now using. Thanks...Marvin -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Mail from Vim Github Repository
El Monday 24 August 2015, Christian Brabandt escribió: 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. Note that the sender name is lost as well. It's difficult to read who said what, so one would want to click on the link and read it on the web anyway. -- Alex (a.k.a. suy) | GPG ID 0x0B8B0BC2 http://barnacity.net/ | http://disperso.net
