<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: On Top Posting</title>
	<atom:link href="http://gfmorris.com/2004/08/09/on-top-posting/feed/" rel="self" type="application/rss+xml" />
	<link>http://gfmorris.com/2004/08/09/on-top-posting/</link>
	<description>The Life and Times of Geof F. Morris</description>
	<lastBuildDate>Thu, 11 Mar 2010 01:03:05 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Geof F. Morris</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3074</link>
		<dc:creator>Geof F. Morris</dc:creator>
		<pubDate>Tue, 10 Aug 2004 22:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3074</guid>
		<description>Kinda like that intentionally obfuscatory comment, Matt?  ;)</description>
		<content:encoded><![CDATA[<p>Kinda like that intentionally obfuscatory comment, Matt?  <img src='http://gfmorris.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3073</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 10 Aug 2004 21:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3073</guid>
		<description>Sometimes the goal of email isn&#039;t to communicate information as clearly as possible.</description>
		<content:encoded><![CDATA[<p>Sometimes the goal of email isn&#8217;t to communicate information as clearly as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the Sage</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3072</link>
		<dc:creator>the Sage</dc:creator>
		<pubDate>Mon, 09 Aug 2004 23:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3072</guid>
		<description>I understand your reasoning, but don&#039;t always think bottom posting is necessary. If I&#039;m answering direct queeries or assertions by the original correspondant, then I&#039;ll use the snip and comment method.</description>
		<content:encoded><![CDATA[<p>I understand your reasoning, but don&#8217;t always think bottom posting is necessary. If I&#8217;m answering direct queeries or assertions by the original correspondant, then I&#8217;ll use the snip and comment method.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geof F. Morris</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3071</link>
		<dc:creator>Geof F. Morris</dc:creator>
		<pubDate>Mon, 09 Aug 2004 17:07:15 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3071</guid>
		<description>&lt;blockquote&gt;To be honest, it generally looks a little sloppy and includes more information than is necessary (it seems polite to get rid of the headers to save your reader(s) time, etc.).&lt;/blockquote&gt;

That&#039;s exactly why I do it.  I may spend a little more time on it, but if my reader spends that much less time reading what I write and understanding it, I feel that it&#039;s time well spent.</description>
		<content:encoded><![CDATA[<blockquote><p>To be honest, it generally looks a little sloppy and includes more information than is necessary (it seems polite to get rid of the headers to save your reader(s) time, etc.).</p></blockquote>
<p>That&#8217;s exactly why I do it.  I may spend a little more time on it, but if my reader spends that much less time reading what I write and understanding it, I feel that it&#8217;s time well spent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3070</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Mon, 09 Aug 2004 17:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3070</guid>
		<description>I prefer the snip-and-post, too. When I started writing and editing for cMW, I learned that way of replying simply because when you&#039;re editing a review/article/etc., you have to provide specific context.

And it does slightly annoy me when people reply with top-posting. To be honest, it generally looks a little sloppy and includes more information than is necessary (it seems polite to get rid of the headers to save your reader(s) time, etc.).</description>
		<content:encoded><![CDATA[<p>I prefer the snip-and-post, too. When I started writing and editing for cMW, I learned that way of replying simply because when you&#8217;re editing a review/article/etc., you have to provide specific context.</p>
<p>And it does slightly annoy me when people reply with top-posting. To be honest, it generally looks a little sloppy and includes more information than is necessary (it seems polite to get rid of the headers to save your reader(s) time, etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://gfmorris.com/2004/08/09/on-top-posting/comment-page-1/#comment-3069</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Mon, 09 Aug 2004 16:37:36 +0000</pubDate>
		<guid isPermaLink="false">http://ijsm.org/archives/2004/08/09/on-top-posting/#comment-3069</guid>
		<description>If I knew how to make my everyday email bottom post, I probably would.  But then I&#039;d have to change it for in-office/out of office replies.</description>
		<content:encoded><![CDATA[<p>If I knew how to make my everyday email bottom post, I probably would.  But then I&#8217;d have to change it for in-office/out of office replies.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
