Andrej Ricnik-Bay wrote:
On 29/05/2008, Bob Pawley [EMAIL PROTECTED] wrote:
... get their point across up front without making me wade through
previous posts which I have already read.
Good for you :}
I can understand the concept of bottom posting
No one advocates bottom-posting
On 29/05/2008, Bob Pawley [EMAIL PROTECTED] wrote:
... get their point across up front without making me wade through
previous posts which I have already read.
Good for you :}
I can understand the concept of bottom posting
No one advocates bottom-posting here. It's all about intersparsed
]
To: Tom Lane [EMAIL PROTECTED]
Cc: Andy Anderson [EMAIL PROTECTED]; Postgres General List
pgsql-general@postgresql.org
Sent: Wednesday, May 28, 2008 11:30 AM
Subject: Re: [GENERAL] Bottom Posting
Tom Lane [EMAIL PROTECTED] writes:
Bottom line: have some respect for your readers. Make it easy
Tom Lane [EMAIL PROTECTED] writes:
Bottom line: have some respect for your readers. Make it easy to
distinguish what you wrote from the preceding material, and remember
that the only reason you are quoting anything at all is to provide some
context for what you are saying. We don't need to
Bob Pawley [EMAIL PROTECTED] writes:
The concept of most lists should be the free exchange of ideas in the most
efficient manner possible.
What is this in response to?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
What do you mean whan you say Don't top post???
http://en.wikipedia.org/wiki/Posting_style
On May 27, 2008, at 7:41 PM, Gregory Williamson wrote:
In-line comments are more readable, especially for longish emails.
The PosgreSQL mail lists all prefer this method. Some related lists
(the
Andy Anderson [EMAIL PROTECTED] writes:
On May 27, 2008, at 7:41 PM, Gregory Williamson wrote:
In-line comments are more readable, especially for longish emails.
But if you do bottom-post, please *do* edit the earlier content down
to just the context of your comments. Otherwise readers
