<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: GTD with Gmail (Part II)</title>
	<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/</link>
	<description>technology where little exists... hacking the simple life</description>
	<pubDate>Sat, 13 Mar 2010 20:48:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Mike512</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-38</link>
		<author>Mike512</author>
		<pubDate>Fri, 22 Apr 2005 14:09:47 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-38</guid>
					<description>Man this is awesome bust some ass and get the third article out.  I am loving it.

Thanks

Mike</description>
		<content:encoded><![CDATA[<p>Man this is awesome bust some ass and get the third article out.  I am loving it.</p>
<p>Thanks</p>
<p>Mike</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ben C.</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-39</link>
		<author>Ben C.</author>
		<pubDate>Fri, 22 Apr 2005 15:57:34 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-39</guid>
					<description>If an email I've received needs action I'll forward it to myself and put the Next Action in the subject line - that way I don't have to read the whole message again if I don't want to.  Too few people harness the awesome power of the subject line.

Looking forward to the next post on GTD and Gmail.</description>
		<content:encoded><![CDATA[<p>If an email I&#8217;ve received needs action I&#8217;ll forward it to myself and put the Next Action in the subject line - that way I don&#8217;t have to read the whole message again if I don&#8217;t want to.  Too few people harness the awesome power of the subject line.</p>
<p>Looking forward to the next post on GTD and Gmail.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: JV</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-40</link>
		<author>JV</author>
		<pubDate>Fri, 22 Apr 2005 16:25:14 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-40</guid>
					<description>I agree with Ben C. Most of my todo emails don't have anything in the message body, in fact.

Interesting idea about using threading for projects --  but then you don't get the aforementioned "awesome power of the subject line".  Usually I'll use threading for follow-up actions, or a history trail.  For instance, if I have a todo to call someone, but get their voice mail, I'll add the message to the "waiting for" label, forward it to myself, and put "left message" or something similarly informative in the message body. </description>
		<content:encoded><![CDATA[<p>I agree with Ben C. Most of my todo emails don&#8217;t have anything in the message body, in fact.</p>
<p>Interesting idea about using threading for projects &#8212;  but then you don&#8217;t get the aforementioned &#8220;awesome power of the subject line&#8221;.  Usually I&#8217;ll use threading for follow-up actions, or a history trail.  For instance, if I have a todo to call someone, but get their voice mail, I&#8217;ll add the message to the &#8220;waiting for&#8221; label, forward it to myself, and put &#8220;left message&#8221; or something similarly informative in the message body.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Hepting</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-51</link>
		<author>Steven Hepting</author>
		<pubDate>Mon, 25 Apr 2005 20:46:50 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-51</guid>
					<description>Suppose you use POP3 to retrieve your Gmail. Is there any way to star your email that way or does the web-based approach work best?</description>
		<content:encoded><![CDATA[<p>Suppose you use POP3 to retrieve your Gmail. Is there any way to star your email that way or does the web-based approach work best?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: bryan</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-53</link>
		<author>bryan</author>
		<pubDate>Mon, 25 Apr 2005 23:16:21 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-53</guid>
					<description>Steven:
Web based is certainly best for me, but if you use a pop mail reader that has some sort of flagging system you could use that.</description>
		<content:encoded><![CDATA[<p>Steven:<br />
Web based is certainly best for me, but if you use a pop mail reader that has some sort of flagging system you could use that.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Sean</title>
		<link>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-63</link>
		<author>Sean</author>
		<pubDate>Wed, 27 Apr 2005 17:11:41 +0000</pubDate>
		<guid>http://spaceagewasteland.com/gtd-with-gmail-part-ii/#comment-63</guid>
					<description>great ideas to harness the power of Gmail, and i'm a GTD conscientious objector ;-)

a minor design suggestion as i go through your posts: a 'home' or 'top' link here at the bottom would keep me from having to scroll back up (i came in to these posts from del.icio.us and didn't go to your main webpage). or just reproduce the same forward and backward navigation you have at the top.

fwiw</description>
		<content:encoded><![CDATA[<p>great ideas to harness the power of Gmail, and i&#8217;m a GTD conscientious objector <img src='http://spaceagewasteland.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>a minor design suggestion as i go through your posts: a &#8216;home&#8217; or &#8216;top&#8217; link here at the bottom would keep me from having to scroll back up (i came in to these posts from del.icio.us and didn&#8217;t go to your main webpage). or just reproduce the same forward and backward navigation you have at the top.</p>
<p>fwiw</p>
]]></content:encoded>
				</item>
</channel>
</rss>
