On Mar 7, 2009, at 02:46, Martin Krischik wrote:

I noticed something annoying about the mailing list: Quite often when I hit reply the reply goes to the original author and not the mailing list.

This always occurs on macports-users and macports-dev. This is intentional, following this reasoning:

http://www.unicom.com/pw/reply-to-harmful.html


I did some experimenting and noticed that this happens when more then
one address is added to "To" address. And this in turn happens when you
just click reply on svn commits.

Maybe we could fine-tune the svn commit posting so that this won't
happen any more.

The lists are configured the way we want them.

On the discussion lists (macports-users and macports-dev), to reply, you should almost always use the "Reply All" feature of your email program so that the reply goes both to the list and to the person who wrote the message you're replying to. If you just use the "Reply" feature your message will only go to the author and not to the list and the list won't benefit from the discussion.

On macports-changes, the Reply-To is set so that you should just "Reply" and your reply will go to macports-dev and to the person who made the commit. It was deliberately set up this way because we want discussion of commits to occur on macports-dev, and just in case the committer is not on macports-dev, the message should go to the committer too. You should not post messages to macports-changes yourself (it is for automated messages from the Subversion repository only) so you should not use "Reply All" or manually address messages to macports-changes.

I am not on macports-tickets so I don't know how it's set up. I would hope it's set up the same way as macports-changes.

I'm not sure how macports-announce is set up. It's announce-only so most people don't have permission to post there. Hopefully that list's Reply To is set to macports-users.


_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to