<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Darcs - The source code management system of the future?</title>
	<link>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/</link>
	<description>About myself and programming</description>
	<pubDate>Wed, 20 Aug 2008 21:27:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Salvatore Iovene &#187; Architecture of patching semantic versus logical content</title>
		<link>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-98</link>
		<author>Salvatore Iovene &#187; Architecture of patching semantic versus logical content</author>
		<pubDate>Mon, 19 Feb 2007 13:45:11 +0000</pubDate>
		<guid>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-98</guid>
		<description>[...] Inspired by a certain patch that hit a darcs repository to which I concur, I would like to talk about one thing that developers don&#8217;t seem to get very often, when using revision control systems: the structure of your files in the repository should have nothing to do with the logical units that make your patches, or with the comment of your patches themselves. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Inspired by a certain patch that hit a darcs repository to which I concur, I would like to talk about one thing that developers don&#8217;t seem to get very often, when using revision control systems: the structure of your files in the repository should have nothing to do with the logical units that make your patches, or with the comment of your patches themselves. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Salvatore Iovene &#187; 5 SVN best practices</title>
		<link>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-87</link>
		<author>Salvatore Iovene &#187; 5 SVN best practices</author>
		<pubDate>Fri, 16 Feb 2007 20:26:12 +0000</pubDate>
		<guid>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-87</guid>
		<description>[...] Versioning systems like CVS, SVN or Darcs are very important tools, that no serious programmers can omit to use. If you started a project without using any versioning tools, I really recommend that you start using one immediately; but I&#8217;m not discussing this right now. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Versioning systems like CVS, SVN or Darcs are very important tools, that no serious programmers can omit to use. If you started a project without using any versioning tools, I really recommend that you start using one immediately; but I&#8217;m not discussing this right now. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Salvatore Iovene &#187; Please drop SVN</title>
		<link>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-55</link>
		<author>Salvatore Iovene &#187; Please drop SVN</author>
		<pubDate>Thu, 08 Feb 2007 12:05:17 +0000</pubDate>
		<guid>http://www.iovene.com/darcs-the-source-code-management-system-of-the-future/#comment-55</guid>
		<description>[...] I have already given a brief introduction to the Darcs source control system, and I would like here to talk about a very strong point it&#8217;s got against SVN. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I have already given a brief introduction to the Darcs source control system, and I would like here to talk about a very strong point it&#8217;s got against SVN. [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
