Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!oliveb!olivey!jerry
From: jerry@olivey.olivetti.com (Jerry Aguirre)
Newsgroups: news.admin
Subject: Re: High Volume Calls For New Approach
Keywords: Signatures;long quotes
Message-ID: <34314@oliveb.olivetti.com>
Date: 15 Dec 88 05:48:02 GMT
References: <26469@bu-cs.BU.EDU> <952@dlhpedg.co.uk>
Sender: news@oliveb.olivetti.com
Reply-To: jerry@olivey.UUCP (Jerry Aguirre)
Organization: Olivetti ATC; Cupertino, Ca
Lines: 15

In article <952@dlhpedg.co.uk> cl@datlog.co.uk (Charles Lambert) writes:
>Mostly,  we use the included text because the followup function delivers it
>on a plate.  I remember using "readnews" when it didn't have that built-in
>convenience;  consequently,  almost never included quotes.  Perhaps cost-
>conscious news administrators should modify all their news reading software
>so that it doesn't give the prepacked inclusion,  or even an environment

Or how about the best of both worlds.  Have the followup function
insert the included text but flag it with something other than ">".
(Except for the attribute.)  Say it gets flagged with "@>" or
something.  Then delete those lines from the text before posting.

This would mean that posters would have to manually select those lines
that they wanted to include and change the prefix string.  (For example
delete the @ at the beginning of the line.)  Yet they would still have
the full text to refer to while composing their response.