<?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: Thoughts about using Git for closed source projects</title>
	<atom:link href="http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/</link>
	<description>Jamie Flournoy's Software Development Blog</description>
	<lastBuildDate>Sat, 12 Jun 2010 04:23:27 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jamie Flournoy</title>
		<link>http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/comment-page-1/#comment-5791</link>
		<dc:creator>Jamie Flournoy</dc:creator>
		<pubDate>Mon, 14 Apr 2008 19:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/#comment-5791</guid>
		<description>Bicker-fests among DVCS weenies bore me. I&#039;m too much of a pragmatist (&quot;fast follower&quot;) to care about every last one. My approach is to stick with Subversion until a DVCS leader emerges, and then try it out to see if it&#039;s time to switch.

I think we&#039;re there right now, and the leader happens to be Git. I think it&#039;s OK (powerful but hard to learn) for hard core developers, probably not for teams where retraining would be an issue and who are happy with what they&#039;re using.

I&#039;m not bothering to evaluate others at this time. I&#039;m working with Rails, and that community is leaning toward Git, so there&#039;s a very high cost to me if I were to use something else for my work and then Git for everybody else&#039;s work (plugins, etc.).</description>
		<content:encoded><![CDATA[<p>Bicker-fests among DVCS weenies bore me. I&#8217;m too much of a pragmatist (&#8221;fast follower&#8221;) to care about every last one. My approach is to stick with Subversion until a DVCS leader emerges, and then try it out to see if it&#8217;s time to switch.</p>
<p>I think we&#8217;re there right now, and the leader happens to be Git. I think it&#8217;s OK (powerful but hard to learn) for hard core developers, probably not for teams where retraining would be an issue and who are happy with what they&#8217;re using.</p>
<p>I&#8217;m not bothering to evaluate others at this time. I&#8217;m working with Rails, and that community is leaning toward Git, so there&#8217;s a very high cost to me if I were to use something else for my work and then Git for everybody else&#8217;s work (plugins, etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam B.</title>
		<link>http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/comment-page-1/#comment-5790</link>
		<dc:creator>Adam B.</dc:creator>
		<pubDate>Mon, 14 Apr 2008 18:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2008/04/14/thoughts-about-using-git-for-closed-source-projects/#comment-5790</guid>
		<description>This is an old article, but how do you think it fares today?
http://blog.ianbicking.org/dvcs-mini-roundup.html</description>
		<content:encoded><![CDATA[<p>This is an old article, but how do you think it fares today?<br />
<a href="http://blog.ianbicking.org/dvcs-mini-roundup.html" rel="nofollow">http://blog.ianbicking.org/dvcs-mini-roundup.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
