From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig James <cjames@emolecules.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: top posting?
Date: Mon, 06 May 2013 14:47:36 -0400
Message-ID: <15001.1367866056@sss.pgh.pa.us> (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>
Craig James <cjames@emolecules.com> writes:
> 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.
Quoting entire messages is rude, IMO, no matter where you attach your
comments. What is respectful of your readers' time is to quote just
enough to remind them what you're responding to. And once you do that,
it's more natural to append your responses after what you're responding
to.
I'm aware that there are a whole lot of people nowadays who don't get
this element of email etiquette, or who use tools that make it hard
to do things that way (suggesting that the tool authors don't get it
either). But that's what's been considered good style for about
three decades, in my book.
> 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.
I think we're on the same page, actually, except for the brief-summary
bit. I'm not sure that a brief summary without context is really all
that efficient or intelligible. It's probably a tenable approach if
there's only a few threads going on at a time, but how often is that a
good assumption? I guess in an ideal world the Subject: line would
provide enough context ... but people aren't terribly good about picking
good subjects to start with, and they're positively bad about adjusting
the Subject: when the thread diverges into sub-topics.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: tgl@sss.pgh.pa.us, cjames@emolecules.com
Subject: Re: top posting?
In-Reply-To: <15001.1367866056@sss.pgh.pa.us>
* 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