Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*too\s+much\s+to\s+read\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*too\s+much\s+to\s+read\s*$/: 5 ]

Total 5 documents matching your query.

1. too much to read (score: 1): Author: Unknown; Date: 12 May 96 13:51:56 EDT; I just got back from a vacation in Germany and was wondering if there was a way to organize or sort the messages on the list to avoid having to sift/scan though forty or fifty letters a day to find t; /html/triumphs/1996-05/msg00382.html (8,393 bytes)
2. Re: too much to read (score: 1): Author: Unknown; Date: Mon, 13 May 1996 23:27:32 +0000; I've just got back from a weekend away, and there were over 100 messages waiting for me, over 90 of which were from the Triumph list. How about separating the TRs from the Spitfires/GT6s/Heralds wit; /html/triumphs/1996-05/msg00416.html (7,794 bytes)
3. Re: too much to read (score: 1): Author: Unknown; Date: Mon, 13 May 1996 22:25:14 -0400 (EDT); I hate to bring this up again, but a solution might be to have a newsgroup working in conjunction with the mailing list. The beauty of the newsgroup is that with a threaded news reader (God's own gif; /html/triumphs/1996-05/msg00421.html (9,260 bytes)
4. re: too much to read (score: 1): Author: Unknown; Date: Tue, 14 May 1996 22:11:30 -0400; Wordly Scions, Not to take away from the descriptive subject lines idea (an excellent idea IMHO). But for those with mailboxes that are filling up with large numbers of messages, there is always the; /html/triumphs/1996-05/msg00453.html (6,630 bytes)
5. Re: too much to read (score: 1): Author: Unknown; Date: Wed, 15 May 1996 10:46:02 +1000; I see I'm not the only one suffering from info overload. I strongly support any solution to filter the - usually valuable - data posted to the list. Due to other time commitments, I currently have ov; /html/triumphs/1996-05/msg00456.html (8,396 bytes)

Current List: 1 - 5
Page: [1]