I meant it's a bit not good situation if user setup `watch` for vim repo in github, meanwhile he's in vim_dev group too, then there would forward Pr/issues/discussion from two sources, and that maybe get loop into dead loop if someone replied one of the mail and got confused the source.
one workaround maybe was keeping vim_dev for dev purpose, and github issues/pr/discussion was there stayed just in github. better solution maybe if there was a way to detect dup mail and not **re-forward** again, but not sure if it was possible? -- shane.xb.qian -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/OS3P286MB09134F849CCC0BE9EC52C9D7EBC6A%40OS3P286MB0913.JPNP286.PROD.OUTLOOK.COM.
