-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue for testing github-sf mailing list integration #74
Comments
res ipsa loquitur |
I only seem to be getting these messages from github; are they making On Thu, 4 Apr 2013, jwpeterson wrote:
Anyone short on musing ideas, feel free to submit your answers to the |
On Thu, Apr 4, 2013 at 10:40 AM, roystgnr notifications@github.com wrote:
Negative. They are all being trapped under the "implicit destination" At least now that the emails are going to the gmail account I created, the On Thu, 4 Apr 2013, jwpeterson wrote:
Hmm... I don't even know how to answer the first question without looking John |
BTW, I did find this thread: http://mail.python.org/pipermail/mailman-users/2006-September/053495.html that would probably allow us to automatically accept the bcc'd/forwarded posts. But do we really want to do that after all? It would most likely force everyone to have to create a mail filter to avoid seeing two copies of everything posted to a github issue. On the other hand, this will effectively be the end of the libmesh-devel mailing list (and its archives, which I've found to be useful in the past) as we know it. You can already see the drop-off in the last month's data... |
I'm already in the habit of unthinkingly deleting the second copy of |
Let me try another email to an on-topic ticket and let's see if I get |
Feel free to post random philosophical musings...
The text was updated successfully, but these errors were encountered: