public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn at home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Quoting
Date: Sun, 31 Jul 2005 09:04:45 -0500	[thread overview]
Message-ID: <04f101c595d8$ce982840$6a00a8c0@desktop> (raw)
In-Reply-To: <Pine.BSF.4.63.0507310815250.37538@server2.shellworld.net>

Also, for anyone else who might not like quoting, if the quoting occurs 
after the message, then it is not a problem for anyone.  I also don't like 
the quoting at the top, because most of the time I don't want to read 
through it, but it is nice to have it below.
Glenn

----- Original Message ----- 
From: "Karen Lewellen" <klewellen@shellworld.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, July 31, 2005 7:19 AM
Subject: Re: Quoting


Lorenzo,
With all due respect, this may not be true.  People are joining all the
time, and even those here are searching the archives when looking for
something.  Sometimes a thread shifts and the first part of it or the
source question   is no longer clear.
Therefore at least in a information based list like this repeating that
message both gives readers a chance to follow  the discussion, and may
even save time in having a topic repeated.
Does this make sense?
Karen

On Sun, 31 Jul 2005, Lorenzo Taylor wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sorry.  I don't quote unless I absolutely have to.  I feel that quoting
> wastes the reader's time since he/she has already read the same message
> once, twice or even 5 times already.  Why should I add to that problem?
>
> Lorenzo
> - --
> - -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d- s:+ a- C+++ UL++++ P+ L+++ E- W++ N o K- w---
> O M V- PS+++ PE Y+ PGP++ t++ 5+ X+ R tv-- b++ DI-- D+
> G e* h---- r+++ y+++
> - ------END GEEK CODE BLOCK------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFC7GycG9IpekrhBfIRAvA7AJ9zxbrRmI7aHxBuPXZgpQuiveTonACgmAOj
> nedF/D8UBBiexS5igbHNObM=
> =O9eN
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup




  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Quoting Christian Gerhardt
 ` Quoting Janina Sajka
   ` Quoting Thomas Stivers
     ` Quoting Hart Larry
       ` Quoting Lorenzo Taylor
         ` Quoting Karen Lewellen
           ` Glenn at home [this message]
             ` Quoting Karen Lewellen
               ` Quoting Gene Collins
     ` Quoting Janina Sajka
   ` Quoting Christian Gerhardt
     ` Quoting Steve Holmes
       ` Quoting Sean McMahon
       ` Quoting Charles Hallenbeck
         ` Quoting Steve Holmes
 Quoting Dawes, Stephen
 ` Quoting Gene Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='04f101c595d8$ce982840$6a00a8c0@desktop' \
    --to=glennervin@cableone.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).