<?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/"
		>
<channel>
	<title>Comments for blog.jacius.info</title>
	<atom:link href="http://blog.jacius.info/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jacius.info</link>
	<description></description>
	<lastBuildDate>Fri, 30 Dec 2011 13:13:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Your Git Submodule and You by AntonK</title>
		<link>http://blog.jacius.info/2009/08/09/your-git-submodule-and-you/comment-page-1/#comment-154</link>
		<dc:creator>AntonK</dc:creator>
		<pubDate>Fri, 30 Dec 2011 13:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://90/2009/08/09/your-git-submodule-and-you#comment-154</guid>
		<description>Nice guidelines!
I wonder is there any possibility to have a super-repository to always point to the HEAD of a submodule?
Developers tend to avoid extra work with advancing/updating references to submodules after committing own changes into a submodule. Anyway we&#039;re developing on the &quot;trunk&quot; (&quot;main branch&quot;) of both main sources and submodules...</description>
		<content:encoded><![CDATA[<p>Nice guidelines!<br />
I wonder is there any possibility to have a super-repository to always point to the HEAD of a submodule?<br />
Developers tend to avoid extra work with advancing/updating references to submodules after committing own changes into a submodule. Anyway we&#8217;re developing on the &#8220;trunk&#8221; (&#8220;main branch&#8221;) of both main sources and submodules&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Git tip: Fix a mistake in a previous commit by davidn</title>
		<link>http://blog.jacius.info/2008/06/22/git-tip-fix-a-mistake-in-a-previous-commit/comment-page-1/#comment-150</link>
		<dc:creator>davidn</dc:creator>
		<pubDate>Sun, 25 Dec 2011 21:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://90/2008/09/06/git-tip-fix-a-mistake-in-a-previous-commit#comment-150</guid>
		<description>You&#039;re right.

Anyway, this post was really usefull for me! Thanks.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right.</p>
<p>Anyway, this post was really usefull for me! Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Git tip: Fix a mistake in a previous commit by Tim</title>
		<link>http://blog.jacius.info/2008/06/22/git-tip-fix-a-mistake-in-a-previous-commit/comment-page-1/#comment-136</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 02 Dec 2011 15:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://90/2008/09/06/git-tip-fix-a-mistake-in-a-previous-commit#comment-136</guid>
		<description>You say: &quot;Look at git log and copy the first 5 or so characters from the ID of the commit you want to edit onto your clipboard.
Start the interactive rebase process, pasting in the characters from the ID: git rebase --interactive ID&quot;
The ID should actually be the &lt;i&gt;parent&lt;/i&gt; of the commit you want to edit.</description>
		<content:encoded><![CDATA[<p>You say: &#8220;Look at git log and copy the first 5 or so characters from the ID of the commit you want to edit onto your clipboard.<br />
Start the interactive rebase process, pasting in the characters from the ID: git rebase &#8211;interactive ID&#8221;<br />
The ID should actually be the <i>parent</i> of the commit you want to edit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ambienome &#8211; Technology by mark</title>
		<link>http://blog.jacius.info/2011/11/13/ambienome-technology/comment-page-1/#comment-115</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Thu, 24 Nov 2011 14:17:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jacius.info/?p=766#comment-115</guid>
		<description>I&#039;m excited!</description>
		<content:encoded><![CDATA[<p>I&#8217;m excited!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sup email client keybindings and filters by Alex Ghitza</title>
		<link>http://blog.jacius.info/2010/11/08/sup-email-client-keybindings-and-filters/comment-page-1/#comment-98</link>
		<dc:creator>Alex Ghitza</dc:creator>
		<pubDate>Tue, 01 Nov 2011 00:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jacius.info/?p=752#comment-98</guid>
		<description>Sorry, I messed up the link, here is the right one: &lt;a href=&quot;http://notmuchmail.org/&quot; rel=&quot;nofollow&quot;&gt;notmuch&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Sorry, I messed up the link, here is the right one: <a href="http://notmuchmail.org/" rel="nofollow">notmuch</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sup email client keybindings and filters by Alex Ghitza</title>
		<link>http://blog.jacius.info/2010/11/08/sup-email-client-keybindings-and-filters/comment-page-1/#comment-97</link>
		<dc:creator>Alex Ghitza</dc:creator>
		<pubDate>Tue, 01 Nov 2011 00:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jacius.info/?p=752#comment-97</guid>
		<description>If you liked parts of sup and you like emacs, maybe &lt;a href=&quot;www.notmuchmail.org&quot; rel=&quot;nofollow&quot;&gt;notmuch&lt;/a&gt; is closer to what you are looking after.</description>
		<content:encoded><![CDATA[<p>If you liked parts of sup and you like emacs, maybe <a href="www.notmuchmail.org" rel="nofollow">notmuch</a> is closer to what you are looking after.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Revision numbers considered harmful by Daniel</title>
		<link>http://blog.jacius.info/2008/06/21/revision-numbers-considered-harmful/comment-page-1/#comment-94</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Wed, 06 Jul 2011 16:07:50 +0000</pubDate>
		<guid isPermaLink="false">http://90/2008/06/21/revision-numbers-considered-harmful#comment-94</guid>
		<description>The only problem is that later, when you look at the log, you see a lot of little commits and have to look hard to find the meaningful ones.
But you can always squash them later (that is, if you didn&#039;t push them yet).</description>
		<content:encoded><![CDATA[<p>The only problem is that later, when you look at the log, you see a lot of little commits and have to look hard to find the meaningful ones.<br />
But you can always squash them later (that is, if you didn&#8217;t push them yet).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Your Git Submodule and You by Pulkit Singhal</title>
		<link>http://blog.jacius.info/2009/08/09/your-git-submodule-and-you/comment-page-1/#comment-90</link>
		<dc:creator>Pulkit Singhal</dc:creator>
		<pubDate>Tue, 31 May 2011 15:49:55 +0000</pubDate>
		<guid isPermaLink="false">http://90/2009/08/09/your-git-submodule-and-you#comment-90</guid>
		<description>Thanks for helping me understand the basics of submodules:
a)Users will not (necessarily) get the most recent revision from the submodule repository. Instead, they will get the revision of the submodule that is recorded in the revision of the main repository they are viewing.
b) To get other people’s changes from upstream (e.g. Github), pull (or fetch + merge) from within the submodule directory.
I was lost without these.</description>
		<content:encoded><![CDATA[<p>Thanks for helping me understand the basics of submodules:<br />
a)Users will not (necessarily) get the most recent revision from the submodule repository. Instead, they will get the revision of the submodule that is recorded in the revision of the main repository they are viewing.<br />
b) To get other people’s changes from upstream (e.g. Github), pull (or fetch + merge) from within the submodule directory.<br />
I was lost without these.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Droplet &#8211; End of Day 3 by ippa</title>
		<link>http://blog.jacius.info/2009/06/28/droplet-end-of-day-3/comment-page-1/#comment-14</link>
		<dc:creator>ippa</dc:creator>
		<pubDate>Sun, 28 Jun 2009 07:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://90/2009/06/28/droplet-end-of-day-3#comment-14</guid>
		<description>lookin&#039; good</description>
		<content:encoded><![CDATA[<p>lookin&#8217; good</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RubyWeekend #3 Game Concept by Jakob</title>
		<link>http://blog.jacius.info/2009/06/26/rubyweekend-3-game-concept/comment-page-1/#comment-13</link>
		<dc:creator>Jakob</dc:creator>
		<pubDate>Fri, 26 Jun 2009 07:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://90/2009/06/26/rubyweekend-3-game-concept#comment-13</guid>
		<description>I think it is a really good concept! And thanks for the link to the polar panorama photos, they were really cool.</description>
		<content:encoded><![CDATA[<p>I think it is a really good concept! And thanks for the link to the polar panorama photos, they were really cool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

