Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt+news@cis.ohio-state.edu>
Subject: Re: posting terminology (was: Automagically fixing replies to bottom quoters?)
Date: Mon, 03 Jun 2002 14:32:33 -0400	[thread overview]
Message-ID: <wc3ofes2oxq.fsf@eta.cis.ohio-state.edu> (raw)
In-Reply-To: <3cfbb346$1_2@nopics.sjc>

Kruskal <kruskal@my-deja.com> writes:

>> I'm confused, don't you mean top posters in the above question?
>> Aren't bottom posting and bottom quoting two different things?  
>
> My mistake.  Should be top-posters (or I guess, bottom-quoters).  :)
> I was so fed up with it I couldn't even name it properly.

I know the feeling, it is maddening!

Maybe gnus could do its part in preventing people from top-posting,
just like it prevents people from posting lines without subjects or
lines >= 79 characters.  Maybe a warning could be issued if there is
no original text below at least one quoted part (ignoring signature).
I think that basically defines top-posting.
-- 
Benjamin


           reply	other threads:[~2002-06-03 18:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3cfbb346$1_2@nopics.sjc>]

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=wc3ofes2oxq.fsf@eta.cis.ohio-state.edu \
    --to=rutt+news@cis.ohio-state.edu \
    /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 NNTP newsgroup(s).