Well for most of us, if we knew the way the email addresses were in the header, we could put in rules to send them to another folder so we need only read them if interested.
Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field.----- Original Message ----- From: "Mesar Hameed" <mesar.hameed@xxxxxxxxx>
To: "Mesar Hameed" <mesar.hameed@xxxxxxxxx> Cc: <nvda-addons@xxxxxxxxxxxxx> Sent: Monday, May 13, 2013 8:16 AM Subject: [nvda-addons] commit emails
Hi all, How do people feel about setting up the bitbucket email notifications/diff to come to the mailing list? This will mean we dont have to maintain a list of interested people for each addon. Idealy we would have something like nvda-commits@xxxxxxxxxxxxxxxxxx, but I don't think its quite appropriate to send addon commit emails there, and/or if we want to maintain another list. Thoughts? Mesar ---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx.To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx.If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx.
---------------------------------------------------------------- NVDA add-ons Central: A list for discussing NVDA add-ons To post a message, send an email to nvda-addons@xxxxxxxxxxxxx. To unsubscribe, send an email with the subject line of "unsubscribe" (without quotes) to nvda-addons-request@xxxxxxxxxxxxx. If you have questions for list moderators, please send a message to nvda-addons-moderators@xxxxxxxxxxxxx.
