pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Stephen Cook <sclists@gmail.com>
To: Craig James <cjames@emolecules.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: top posting?
Date: Tue, 07 May 2013 03:37:07 -0400
Message-ID: <5188AF23.9040203@gmail.com> (raw)
In-Reply-To: <CAFwQ8rftO5Z6tMs6pAbfne9noDMGtp7sJfq+rZvJ-BtT5nuw1w@mail.gmail.com>
References: <CAFwQ8rftO5Z6tMs6pAbfne9noDMGtp7sJfq+rZvJ-BtT5nuw1w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On 5/6/2013 2:15 PM, Craig James wrote:
> Just out of curiousity, I see comments like this all the time:
>
> > (*please* stop top-posting).
>
> I've been participating in newsgroups since UUCP days, and I've never 
> encountered a group before that encouraged bottom posting. Bottom 
> posting has traditionally been considered rude -- it forces readers to 
> scroll, often through pages and pages of text, to see a few lines of 
> original material.
>
> The most efficient strategy, one that respects other members' time, is 
> to briefly summarize your point at the TOP of a posting, then to 
> *briefly* quote only the relevant parts of the post to which you are 
> replying, and bottom-post after the quoted text. That lets your reader 
> quickly see if it's relevant or not, and move on to the next post.
>
> Contributors in these newsgroups seem to think it's OK to quote five 
> pages of someone else's response, then add one or two sentences at the 
> bottom ... it's just laziness that forces readers to wade through the 
> same stuff over and over in each thread.
>
> How did the Postgres newsgroups get started with this "only bottom 
> post" idea?
>
> (I'm not trying to start a flame war, just genuinely curious.)
>
> Craig

I always feel good when I see this post, it means I've been following a 
mailing list for a (relatively) long time...

It doesn't matter to me at all, I just go with whatever is generally 
accepted by the mailing list (or perhaps, whatever is generally accepted 
by the most vocal part of the mailing list). Although, I only ever 
really did the whole "inline snippets" thing when I'm tearing someone up 
in a flame war. Most other replies don't require the precision-quoting.

Currently I'm using Thunderbird, a web page, or various mobile apps to 
check my email, and all of them mark the quoted part well enough that I 
can skip it and see what is new, or read it knowing full well it is a 
quote. Haven't done text-only email for ages, but even back then I 
believe there were markings in the margin for what was a quote and what 
was new content.

-- Stephen



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (25+ messages)  latest in thread

Message-ID: <5188AF23.9040203@gmail.com>
Permalink:  ../5188AF23.9040203@gmail.com/
Also on:    postgresql.org/message-id/5188AF23.9040203@gmail.com

 · 

reply

Reply instructions:

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

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: sclists@gmail.com, cjames@emolecules.com
  Subject: Re: top posting?
  In-Reply-To: <5188AF23.9040203@gmail.com>

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

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox