Re: Re: PHP RFC # 0001 --- List Etiquette

On Nov 28, 2007 11:13 AM, <news_yodpeirs@thoftware.de> wrote: > Wouldn't this be solved if the email is simply an answer to the thread > instead of a new, separate email? Within the thread about nested files > (http://www.nabble.com/Nested-include-require-not-working-in-5.2-tf4882937.html) > there was also an email with a changed subject ("(SOLVED)" was added), but > it stays in the thread as it was an answer to the thread. I think, the main > problem is, not to answer to the thread but simply sending a new email. > > Thomas > > -- > > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > Thomas, You're exactly right, which is something else I failed to include in the original email. Hence the "Request For Comments" style. It usually is only when the user sends a new message to the list, forwards it, copy-and-pastes it, et cetera. However, sometimes it will create a new thread even upon doing a reply-all to the list with a subject change. Whether the client changes the email ID based on that or what, I honestly don't know the answer, but the 5.2.3 segfault message is yet again a relevant example. Zbignew actually did just hit reply-all on that one. Further, I think Jason Pruim's suggestion of adding to the welcome email opens up an interesting point. Can the NEWBIE GUIDE that Jay Blanchard, et al, have co-created be included in the welcome mail? For people who actually want to be a part of this mailing list community, it would be a great get-acquainted README-style message that could help prevent some flames. -- Daniel P. Brown [office] (570-) 587-7080 Ext. 272 [mobile] (570-) 766-8107 If at first you don't succeed, stick to what you know best so that you can make enough money to pay someone else to do it for you.