<?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 for Version Control</title>
	<atom:link href="http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/</link>
	<description>programming, technology and human behavior</description>
	<lastBuildDate>Thu, 17 Nov 2011 13:56:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Appropriate Checkin Comments &#171; MTR</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-24229</link>
		<dc:creator>Appropriate Checkin Comments &#171; MTR</dc:creator>
		<pubDate>Thu, 17 Nov 2011 13:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-24229</guid>
		<description>[...] One developer writes: Many developers are sloppy about commenting their changes, and some may feel that commit messages are not needed. Either they consider the changes trivial, or they argue that you can just inspect the revision history to see what was changed. However, the revision history only shows what was actually changed, not what the programmer intended to do, or why the change was made. This can be even more problematic when people don’t do fine-grained commits, but rather submit a week’s worth of changes to multiple modules in one large pile. With a fine-grained revision history, comments can be useful to distinguish trivial from non-trivial changes in the repository. In my opinion, if the changes you made are not important enough to comment on, they probably are not worth committing either. [...]</description>
		<content:encoded><![CDATA[<p>[...] One developer writes: Many developers are sloppy about commenting their changes, and some may feel that commit messages are not needed. Either they consider the changes trivial, or they argue that you can just inspect the revision history to see what was changed. However, the revision history only shows what was actually changed, not what the programmer intended to do, or why the change was made. This can be even more problematic when people don’t do fine-grained commits, but rather submit a week’s worth of changes to multiple modules in one large pile. With a fine-grained revision history, comments can be useful to distinguish trivial from non-trivial changes in the repository. In my opinion, if the changes you made are not important enough to comment on, they probably are not worth committing either. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suggestions for a good commit message: format/guideline? - Programmers Goodies</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-19798</link>
		<dc:creator>Suggestions for a good commit message: format/guideline? - Programmers Goodies</dc:creator>
		<pubDate>Mon, 04 Jul 2011 16:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-19798</guid>
		<description>[...] Here&#8217;s an extract from my recommended best practices for version control: [...]</description>
		<content:encoded><![CDATA[<p>[...] Here&#8217;s an extract from my recommended best practices for version control: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Practices to Consider When Using a Version Control Tool &#124; Version Control Notes</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-6235</link>
		<dc:creator>Best Practices to Consider When Using a Version Control Tool &#124; Version Control Notes</dc:creator>
		<pubDate>Wed, 23 Jun 2010 00:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-6235</guid>
		<description>[...] within a version control system.  If you would like to read the full article, you can find it at: http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/.          This entry was posted in Uncategorized. Bookmark the permalink.    &#8592; Seven Basics [...]</description>
		<content:encoded><![CDATA[<p>[...] within a version control system.  If you would like to read the full article, you can find it at: <a href="http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/" rel="nofollow">http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/</a>.          This entry was posted in Uncategorized. Bookmark the permalink.    &larr; Seven Basics [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: naplan</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-5836</link>
		<dc:creator>naplan</dc:creator>
		<pubDate>Tue, 18 May 2010 01:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-5836</guid>
		<description>What do you think about Visual Source Safe in comparison to CVS. Thanks for the post.</description>
		<content:encoded><![CDATA[<p>What do you think about Visual Source Safe in comparison to CVS. Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego Vieira</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-4201</link>
		<dc:creator>Diego Vieira</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-4201</guid>
		<description>Very usefull tips!
Thanks Anders</description>
		<content:encoded><![CDATA[<p>Very usefull tips!<br />
Thanks Anders</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Cantrell</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-2815</link>
		<dc:creator>Dave Cantrell</dc:creator>
		<pubDate>Sat, 12 Dec 2009 00:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-2815</guid>
		<description>Anders,

Just wanted to say this is a great post. I was looking for exactly this kind of information and you summed everything up very nicely. Thanks for the info!</description>
		<content:encoded><![CDATA[<p>Anders,</p>
<p>Just wanted to say this is a great post. I was looking for exactly this kind of information and you summed everything up very nicely. Thanks for the info!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daily Links &#124; AndySowards.com :: Professional Web Design, Development, Programming, Hacks, Downloads, Math and being a Web 2.0 Hipster?</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-50</link>
		<dc:creator>Daily Links &#124; AndySowards.com :: Professional Web Design, Development, Programming, Hacks, Downloads, Math and being a Web 2.0 Hipster?</dc:creator>
		<pubDate>Thu, 08 Jan 2009 01:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-50</guid>
		<description>[...] Best Practices for Version Control « loop label Good Version Control Tips for Programmers! (tags: blog svn programming best standards bestpractices practices subversion sourcecontrol git versioncontrol tips) [...]</description>
		<content:encoded><![CDATA[<p>[...] Best Practices for Version Control « loop label Good Version Control Tips for Programmers! (tags: blog svn programming best standards bestpractices practices subversion sourcecontrol git versioncontrol tips) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian St. Pierre</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-49</link>
		<dc:creator>Brian St. Pierre</dc:creator>
		<pubDate>Wed, 07 Jan 2009 17:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-49</guid>
		<description>Anders, thanks for this list. I&#039;ve combined this with some thoughts from others and just posted this: http://blog.bstpierre.org/version-control-habits

Interested in any feedback you might have on the topic. Thanks!

-Brian</description>
		<content:encoded><![CDATA[<p>Anders, thanks for this list. I&#8217;ve combined this with some thoughts from others and just posted this: <a href="http://blog.bstpierre.org/version-control-habits" rel="nofollow">http://blog.bstpierre.org/version-control-habits</a></p>
<p>Interested in any feedback you might have on the topic. Thanks!</p>
<p>-Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Veera</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-48</link>
		<dc:creator>Veera</dc:creator>
		<pubDate>Thu, 30 Oct 2008 10:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-48</guid>
		<description>Very useful information.

Also if possible, could you please share some links to effectively use &#039;trunk&#039; and &#039;branch&#039; in Subversion?

Thanks.</description>
		<content:encoded><![CDATA[<p>Very useful information.</p>
<p>Also if possible, could you please share some links to effectively use &#8216;trunk&#8217; and &#8216;branch&#8217; in Subversion?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders Sandvig</title>
		<link>http://blog.looplabel.net/2008/07/28/best-practices-for-version-control/comment-page-1/#comment-46</link>
		<dc:creator>Anders Sandvig</dc:creator>
		<pubDate>Thu, 21 Aug 2008 19:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://looplabel.wordpress.com/?p=63#comment-46</guid>
		<description>You may also want to check out &lt;a href=&quot;http://www.codinghorror.com/blog/archives/001165.html&quot; rel=&quot;nofollow&quot;&gt;this interesting discussion on work cycles and commit frequencies (Coding Horror)&lt;/a&gt; and &lt;a href=&quot;http://techrockguy.blogspot.com/2008/05/source-control-with-continuous.html&quot; rel=&quot;nofollow&quot;&gt;these notes on using version control with continuous integration systems (Tech Rock Guy)&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>You may also want to check out <a href="http://www.codinghorror.com/blog/archives/001165.html" rel="nofollow">this interesting discussion on work cycles and commit frequencies (Coding Horror)</a> and <a href="http://techrockguy.blogspot.com/2008/05/source-control-with-continuous.html" rel="nofollow">these notes on using version control with continuous integration systems (Tech Rock Guy)</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

