<?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 on: git Submodules Explained</title>
	<atom:link href="http://longair.net/blog/2010/06/02/git-submodules-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://longair.net/blog/2010/06/02/git-submodules-explained/</link>
	<description>(occasional miscellanea)</description>
	<lastBuildDate>Thu, 26 Apr 2012 21:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Henning Glatter-Gotz</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-64155</link>
		<dc:creator>Henning Glatter-Gotz</dc:creator>
		<pubDate>Fri, 23 Mar 2012 15:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-64155</guid>
		<description>Mark, nice post that helped me sort out some things while moving from SVN to git. The link referenced at the bottom of the post has a 404 (http://git.wiki.kernel.org/index.php/GitSubmoduleTutorial)</description>
		<content:encoded><![CDATA[<p>Mark, nice post that helped me sort out some things while moving from SVN to git. The link referenced at the bottom of the post has a 404 (<a href="http://git.wiki.kernel.org/index.php/GitSubmoduleTutorial" rel="nofollow">http://git.wiki.kernel.org/index.php/GitSubmoduleTutorial</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Turner (@phantomwhale)</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-42819</link>
		<dc:creator>Ben Turner (@phantomwhale)</dc:creator>
		<pubDate>Thu, 22 Sep 2011 01:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-42819</guid>
		<description>Once more I have git knowledge gaps, and once more I find myself hitting your blog via the Google ! Another great post, dude, not only answering my question, but then the next four or five questions that immediately followed ;)</description>
		<content:encoded><![CDATA[<p>Once more I have git knowledge gaps, and once more I find myself hitting your blog via the Google ! Another great post, dude, not only answering my question, but then the next four or five questions that immediately followed ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An M</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-17150</link>
		<dc:creator>An M</dc:creator>
		<pubDate>Tue, 08 Feb 2011 13:20:42 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-17150</guid>
		<description>I love 1.7&#039;s git st</description>
		<content:encoded><![CDATA[<p>I love 1.7&#8242;s git st</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-6779</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Wed, 25 Aug 2010 10:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-6779</guid>
		<description>szg: yes, I know what you mean - in fact, I&#039;m finding the new behaviour increasingly helpful as I get used to it, although the time taken for &quot;git status&quot; is often infuriating .  I suppose I mostly object to the way that such a change was introduced: I think was unfriendly to the users, especially since the options to revert to the existing behaviour are only appearing in later versions now...</description>
		<content:encoded><![CDATA[<p>szg: yes, I know what you mean &#8211; in fact, I&#8217;m finding the new behaviour increasingly helpful as I get used to it, although the time taken for &#8220;git status&#8221; is often infuriating .  I suppose I mostly object to the way that such a change was introduced: I think was unfriendly to the users, especially since the options to revert to the existing behaviour are only appearing in later versions now&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: szg</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-6724</link>
		<dc:creator>szg</dc:creator>
		<pubDate>Sun, 22 Aug 2010 19:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-6724</guid>
		<description>I actually prefer the git 1.7 submodule behaviour. With the older git I&#039;ve forgotten to commit in a submodule for nearly a year in a project. Now both git status and git diff show me I&#039;ve done some changes there. The git 1.7 release notes refer to such cases as a justification. I think that the former lightning-fast git-status in a big project with the bulk of the stuff in submodules was just and ILLUSION, both in terms of speed and output. I&#039;m sure you never ever forget about changes in your submodules, but as for me, I&#039;m very very stupid. Git 1.7 is my friend.</description>
		<content:encoded><![CDATA[<p>I actually prefer the git 1.7 submodule behaviour. With the older git I&#8217;ve forgotten to commit in a submodule for nearly a year in a project. Now both git status and git diff show me I&#8217;ve done some changes there. The git 1.7 release notes refer to such cases as a justification. I think that the former lightning-fast git-status in a big project with the bulk of the stuff in submodules was just and ILLUSION, both in terms of speed and output. I&#8217;m sure you never ever forget about changes in your submodules, but as for me, I&#8217;m very very stupid. Git 1.7 is my friend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-6337</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Fri, 06 Aug 2010 15:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-6337</guid>
		<description>There should be a config option for that soon:

  http://www.spinics.net/lists/git/msg136891.html</description>
		<content:encoded><![CDATA[<p>There should be a config option for that soon:</p>
<p>  <a href="http://www.spinics.net/lists/git/msg136891.html" rel="nofollow">http://www.spinics.net/lists/git/msg136891.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-6273</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Tue, 03 Aug 2010 09:44:23 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-6273</guid>
		<description>VonC: thanks for pointing that out - I hadn&#039;t realized that those changes were in a released version yet.  I will update the post.

It&#039;s a shame that there doesn&#039;t (yet?) seem to be a config option that can set a particular --ignore-submodules setting as a default.</description>
		<content:encoded><![CDATA[<p>VonC: thanks for pointing that out &#8211; I hadn&#8217;t realized that those changes were in a released version yet.  I will update the post.</p>
<p>It&#8217;s a shame that there doesn&#8217;t (yet?) seem to be a config option that can set a particular &#8211;ignore-submodules setting as a default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VonC</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-6257</link>
		<dc:creator>VonC</dc:creator>
		<pubDate>Mon, 02 Aug 2010 07:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-6257</guid>
		<description>Git 1.7.2 (http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.txt) seems to want to alleviate the &#039;git status&#039; issue, by adding the &quot;--ignore-submodules&quot; option.</description>
		<content:encoded><![CDATA[<p>Git 1.7.2 (<a href="http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.txt" rel="nofollow">http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.7.2.txt</a>) seems to want to alleviate the &#8216;git status&#8217; issue, by adding the &#8220;&#8211;ignore-submodules&#8221; option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-5245</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Wed, 02 Jun 2010 14:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-5245</guid>
		<description>Thanks for the pointer, William - I hadn&#039;t looked properly at repo, but I certainly shall.</description>
		<content:encoded><![CDATA[<p>Thanks for the pointer, William &#8211; I hadn&#8217;t looked properly at repo, but I certainly shall.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William</title>
		<link>http://longair.net/blog/2010/06/02/git-submodules-explained/comment-page-1/#comment-5244</link>
		<dc:creator>William</dc:creator>
		<pubDate>Wed, 02 Jun 2010 13:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://longair.net/blog/?p=446#comment-5244</guid>
		<description>Git is awesome for managing a tree, but when you start to try to manage a forest with submodules, things get ugly (to my taste anyway).

I like google&#039;s repo:
http://google-opensource.blogspot.com/2008/11/gerrit-and-repo-android-source.html

Repo isn&#039;t used to replace git. You use git to manage your tree, and repo to manage your forest.</description>
		<content:encoded><![CDATA[<p>Git is awesome for managing a tree, but when you start to try to manage a forest with submodules, things get ugly (to my taste anyway).</p>
<p>I like google&#8217;s repo:<br />
<a href="http://google-opensource.blogspot.com/2008/11/gerrit-and-repo-android-source.html" rel="nofollow">http://google-opensource.blogspot.com/2008/11/gerrit-and-repo-android-source.html</a></p>
<p>Repo isn&#8217;t used to replace git. You use git to manage your tree, and repo to manage your forest.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

