Path: utzoo!attcan!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery
From: allbery@ncoast.UUCP (Brandon S. Allbery)
Newsgroups: news.misc
Subject: Re: Subject lines, -S and KILL files: a suggestion.
Message-ID: <12667@ncoast.UUCP>
Date: 9 Oct 88 16:06:44 GMT
References: <469@snjsn1.SJ.ATE.SLB.COM> <426@gonzo.UUCP> <1490@basser.oz> <112@lucretia.esa.oz> <14940@agate.BERKELEY.EDU>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: news.misc
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 22

As quoted from <14940@agate.BERKELEY.EDU> by weemba@garnet.berkeley.edu (Obnoxious Math Grad Student):
+---------------
| In article <112@lucretia.esa.oz>, tim@lucretia (Tim Bunce) writes:
| >What I'd like to suggest is that a 'comment' character (for example a semi-
| >colon) be introduced into subject lines. The character, and any text that
| >follows it could be ignored by rn for the purposes of subject searching and
| >KILLing but archiving could proceed unhindered.
| 
| >	e.g.:   Subject: Multi-user, real-time, 3D game; (part 1 of 273)
| >	or      Subject: Re: Original subject line; new comment
| 
| How about parentheses?  After all, it's the comment for "From:"
+---------------

I can see it now:  RFC976-compliant Subject: lines!     ;-}

++Brandon
-- 
Brandon S Allbery uunet!hal.cwru.edu!ncoast!allbery allbery%ncoast@hal.cwru.edu
(LAST RESORT ONLY:  allbery@uunet.uu.net)			DELPHI: ALLBERY
comp.sources.misc is moving off ncoast -- please do NOT send submissions direct
	  "So many articles, so little time...."  -- The Line-Eater