<?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: Best Practices With Version Control</title>
	<atom:link href="http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/</link>
	<description>The art, science and business of independent game development</description>
	<lastBuildDate>Sun, 25 Jul 2010 17:51:13 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AntonMills</title>
		<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/comment-page-1/#comment-13972</link>
		<dc:creator>AntonMills</dc:creator>
		<pubDate>Wed, 17 Feb 2010 14:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamepoetry.com/blog/?p=557#comment-13972</guid>
		<description>&lt;p&gt;Good tips, could I possibly add two points to the &quot;Write Comments In Your Commit Message&quot; heading.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;When writing comments in the commit message, ensure that the comments are short concise details of what was added in this commit, not huge explanations of why you did these changes, thats for the code comments! &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;-The other is to always add messages of what you have changed, not what you are planning on changing! All to often I&#039;ve seen others write messages that their committing before doing so-and-so but this can make a history lookup pretty confusing, especially if you don&#039;t get around to adding that feature in the next commit!&lt;/p&gt;

&lt;p&gt;Great post!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Good tips, could I possibly add two points to the &#8220;Write Comments In Your Commit Message&#8221; heading.</p>

<ul>
<li>When writing comments in the commit message, ensure that the comments are short concise details of what was added in this commit, not huge explanations of why you did these changes, thats for the code comments! </li>
</ul>

<p>-The other is to always add messages of what you have changed, not what you are planning on changing! All to often I&#8217;ve seen others write messages that their committing before doing so-and-so but this can make a history lookup pretty confusing, especially if you don&#8217;t get around to adding that feature in the next commit!</p>

<p>Great post!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Version Control with Git, Flash and AS3 — Michael James Williams</title>
		<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/comment-page-1/#comment-13289</link>
		<dc:creator>Version Control with Git, Flash and AS3 — Michael James Williams</dc:creator>
		<pubDate>Wed, 03 Feb 2010 14:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamepoetry.com/blog/?p=557#comment-13289</guid>
		<description>&lt;p&gt;[...] a commit. If in doubt, commit. It&#8217;ll make things much easier in the long run. Check out this post over at gamepoetry for more good [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] a commit. If in doubt, commit. It&#8217;ll make things much easier in the long run. Check out this post over at gamepoetry for more good [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: urbansquall</title>
		<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/comment-page-1/#comment-3651</link>
		<dc:creator>urbansquall</dc:creator>
		<pubDate>Thu, 28 May 2009 18:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamepoetry.com/blog/?p=557#comment-3651</guid>
		<description>&lt;p&gt;Google is always the best place to start. I&#039;m more than happy to answer any questions you might have though.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Google is always the best place to start. I&#8217;m more than happy to answer any questions you might have though.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas</title>
		<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/comment-page-1/#comment-3650</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Thu, 28 May 2009 18:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamepoetry.com/blog/?p=557#comment-3650</guid>
		<description>&lt;p&gt;Nice article, good points.&lt;/p&gt;

&lt;p&gt;I actually haven&#039;t used any form of version control, as I am pretty much the only developer in all my projects, so I had some trouble with some of the words that are unique to experienced users. Is there anywhere out there that covers the terminology, and perhaps some basic introduction to version control?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Nice article, good points.</p>

<p>I actually haven&#8217;t used any form of version control, as I am pretty much the only developer in all my projects, so I had some trouble with some of the words that are unique to experienced users. Is there anywhere out there that covers the terminology, and perhaps some basic introduction to version control?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: A Freelancer&#8217;s Flash Bash [2] &#124; Freelance Flash Games News</title>
		<link>http://www.gamepoetry.com/blog/2009/05/15/best-practices-with-version-control/comment-page-1/#comment-3414</link>
		<dc:creator>A Freelancer&#8217;s Flash Bash [2] &#124; Freelance Flash Games News</dc:creator>
		<pubDate>Fri, 22 May 2009 16:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.gamepoetry.com/blog/?p=557#comment-3414</guid>
		<description>&lt;p&gt;[...] gives some good tips on using Version Control. Follow them, and your team members won&#8217;t have to get angry at [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] gives some good tips on using Version Control. Follow them, and your team members won&#8217;t have to get angry at [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.228 seconds -->
