On Nov 28, 2007 11:16 AM, Jay Blanchard <jblanchard@xxxxxxxxxx> wrote:
> [snip]
> However, doing this defeats the purpose of a mailing list archive,
> and prompts unnecessary repetition of help requests for an issue that
> may have been "discussed to death" just five days prior. Again, the
> [SOLVED] tag is great on a forum, where you can quickly scan for that
> topic that you know has a solution. However, on a mailing list it
> only serves to create confusion, separation of problem and solution,
> and exasperation on behalf of the searcher when viewing the issue on a
> search engine or in the archives.
> [/snip]
>
> I just wanted to point out that putting SOLVED on a mailing list subject
> line has been SOP since the dawn of mailing lists on ARPANet
>
Yeah, I know, and I certainly hope you realize I'm not shooting
you down on that either. Even in the list itself it makes some sense,
as we can see that the issue has been solved. However, due to the
threading of the message it still separates it, so even a user who may
have been away for a few days may not notice that the issue was
resolved, and may respond to a defunct thread.
--
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.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
