Re: [GENERAL] Bottom Posting
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 here. It's all about intersparsed with relevant bits left standing. The concept of most lists should be the free exchange of ideas in the most efficient manner possible. Which is per agreement on the list intersparsed. Which also allows people only just hopping onto the train of thought to get a good understanding of what a thread is about without having to read the lot top to bottom. May not match your individual preference, but then that's not what the list is about, either. Don't forget adding a blank line between quoted text and your reply; that is helpful too. -- Bruce Momjian [EMAIL PROTECTED]http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] 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 with relevant bits left standing. The concept of most lists should be the free exchange of ideas in the most efficient manner possible. Which is per agreement on the list intersparsed. Which also allows people only just hopping onto the train of thought to get a good understanding of what a thread is about without having to read the lot top to bottom. May not match your individual preference, but then that's not what the list is about, either. Bob Cheers, Andrej -- Please don't top post, and don't use HTML e-Mail :} Make your quotes concise. http://www.american.edu/econ/notes/htmlmail.htm -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Bottom Posting
IMHO and WADR I am on four different types of lists. When I am following a thread I very much appreciate those respondents who get their point across up front without making me wade through previous posts which I have already read. I can understand the concept of bottom posting as a means of easily generating digests. However, digests don't seem to be an issue on any of the lists to which I subscribe. The concept of most lists should be the free exchange of ideas in the most efficient manner possible. Bob - Original Message - From: Gregory Stark [EMAIL PROTECTED] 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 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 re-read the entire darn thread. I don't think the people who top-post or quote the entire message are doing it out of disrespect. They just have never been exposed to the traditional style. The main reason I posted this was to demonstrate that there's really no reason to quote the original message. My response was only to this one point and not the longer previous point. I actually think this is a more important point to get across than simply don't top post which just seems to generate lots of bottom posts that are just as bad. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Bottom Posting
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 re-read the entire darn thread. I don't think the people who top-post or quote the entire message are doing it out of disrespect. They just have never been exposed to the traditional style. The main reason I posted this was to demonstrate that there's really no reason to quote the original message. My response was only to this one point and not the longer previous point. I actually think this is a more important point to get across than simply don't top post which just seems to generate lots of bottom posts that are just as bad. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Bottom Posting
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! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Bottom Posting
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 postGis list for instance) have a preponderance of top-quoting. It is always best to try to follow local style. But if you do bottom-post, please *do* edit the earlier content down to just the context of your comments. Otherwise readers can end up paging through lots of stuff before they get to the new bits. Archives are available for reference if necessary. (Oh, and sometimes it's a good idea to change the subject line, too ... though I'm hardly innocent there ;-) Cheers, -- Andy
Re: [GENERAL] Bottom Posting
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 can end up paging through lots of stuff before they get to the new bits. Archives are available for reference if necessary. Indeed. Another little tip that some folk seem not to have figured out: leave some white space between what you write and what you quote. The posts that I hate even worse than top-posting are the ones where the poster quotes the entire thread and inserts a line or two of comment that isn't visibly separate from what's around it, like this: blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah comment added here blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah This is a truly outstanding way of ensuring that no one will read what you wrote. 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 re-read the entire darn thread. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
