Re: Hijack!

From: Steve Atkins <steve(at)blighty(dot)com>
To: General PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Hijack!
Date: 2007-12-11 17:46:24
Message-ID: 46D42AF4-21C7-42C6-ADDB-FF765E84F18B@blighty.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Dec 11, 2007, at 9:40 AM, Tom Lane wrote:

> Steve Atkins <steve(at)blighty(dot)com> writes:
>> In the business world it's common to top-post and not cut previous
>> content
>> - and often appropriate, as it tends to be a communication between a
>> smaller number of people, and the uncut content provides context for
>> future reference.
>
>> Those who rant about anyone who top posts, or state that you should
>> never top-post are mostly clueless or arrogant, or are making over-
>> broad
>> generalizations.
>
> Sure, there are contexts where that makes sense. On the PostgreSQL
> lists, however, you are writing for the archives as much as for the
> immediate readers (and if you don't understand that, *that* is the
> first
> thing you need to learn). The in-line, trimmed-quotations style is a
> lot easier to read when looking through a thread in the archives.
> Another advantage is that trimming quoted text reduces the number of
> useless matches when searching the archives.

Which is pretty much what I said in the relevant context you removed.

The risk of removing the wrong context is that it makes it look like
we're disagreeing. :)

> In short: this is the community consensus on how to post, there are
> good reasons for it, and we need to try to educate newbies in it.
> Not just say "it's okay to ignore the conventions".

Cheers,
Steve

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2007-12-11 17:47:27 Re: Hijack!
Previous Message Tom Lane 2007-12-11 17:45:44 Re: partitioned table query question