<?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: Source code management craziness</title>
	<atom:link href="http://www.xmonk.org/2007/06/08/source-code-management-crazyness-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xmonk.org/2007/06/08/source-code-management-crazyness-2/</link>
	<description>Not much, not less</description>
	<lastBuildDate>Fri, 01 Jul 2011 01:58:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: xmonk</title>
		<link>http://www.xmonk.org/2007/06/08/source-code-management-crazyness-2/comment-page-1/#comment-51</link>
		<dc:creator>xmonk</dc:creator>
		<pubDate>Mon, 11 Jun 2007 14:44:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.xmonk.org/?p=32#comment-51</guid>
		<description>Well, the main problem is that merging with SVN and CVS can, and in most
cases it&#039;s a pain, so this tools make merging quite simple, intelligent and fast, I know the OpenBSD guys are working hard on their own CVS, and hopefully they will find a way to make merging, moving files, etc.. less traumatic.

The problem with SVN, is that to some SVN as a project failed (and Linus agrees with that) I don&#039;t have an opinion on the matter, however it is true that what it is now, it&#039;s just a SCM that makes some things that are hard to do in CVS, easier, and vice-versa, then there is the small issue that merging in SVN is as painful or more so than with CVS.

So the premise of all the tools above, is that both SVN and CVS have been badly design, and because of this, starting from scratch is the way to go, to avoid repeating the same problems.</description>
		<content:encoded><![CDATA[<p>Well, the main problem is that merging with SVN and CVS can, and in most<br />
cases it&#8217;s a pain, so this tools make merging quite simple, intelligent and fast, I know the OpenBSD guys are working hard on their own CVS, and hopefully they will find a way to make merging, moving files, etc.. less traumatic.</p>
<p>The problem with SVN, is that to some SVN as a project failed (and Linus agrees with that) I don&#8217;t have an opinion on the matter, however it is true that what it is now, it&#8217;s just a SCM that makes some things that are hard to do in CVS, easier, and vice-versa, then there is the small issue that merging in SVN is as painful or more so than with CVS.</p>
<p>So the premise of all the tools above, is that both SVN and CVS have been badly design, and because of this, starting from scratch is the way to go, to avoid repeating the same problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tamgo</title>
		<link>http://www.xmonk.org/2007/06/08/source-code-management-crazyness-2/comment-page-1/#comment-52</link>
		<dc:creator>tamgo</dc:creator>
		<pubDate>Mon, 11 Jun 2007 12:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.xmonk.org/?p=32#comment-52</guid>
		<description>I doubt the result of this feud will be an easier life for developers. I mean, all of the projects stated here are open source projects. Maybe with different ideals and/or communities backing them, but still open source projects. If the objective was to make a SCM better for the community, why not collaborate on an existing project? Why not work on top of what has been done and make it better? Are CVS and SVN so fundamentally screwed up that the only alternative was to create something from scratch?

Everyone wants to pimp their implementation. I have not yet seen the video with Torvalds, but I doubt his case is any different.

Right now, I will stick with what I now how to use and solves my problems, which is SVN. It&#039;s not perfect, I have had some troubles with it in the past, but it&#039;s not half bad most of the time. I am also forced to used a proprietary and sucky SCM at work, but that is another story all together. Let&#039;s let these guys fight it out. Whenever they decide what&#039;s the next de facto standard, please let me know, and I&#039;ll consider switching. In the mean time, got too much coding to do to pay attention.</description>
		<content:encoded><![CDATA[<p>I doubt the result of this feud will be an easier life for developers. I mean, all of the projects stated here are open source projects. Maybe with different ideals and/or communities backing them, but still open source projects. If the objective was to make a SCM better for the community, why not collaborate on an existing project? Why not work on top of what has been done and make it better? Are CVS and SVN so fundamentally screwed up that the only alternative was to create something from scratch?</p>
<p>Everyone wants to pimp their implementation. I have not yet seen the video with Torvalds, but I doubt his case is any different.</p>
<p>Right now, I will stick with what I now how to use and solves my problems, which is SVN. It&#8217;s not perfect, I have had some troubles with it in the past, but it&#8217;s not half bad most of the time. I am also forced to used a proprietary and sucky SCM at work, but that is another story all together. Let&#8217;s let these guys fight it out. Whenever they decide what&#8217;s the next de facto standard, please let me know, and I&#8217;ll consider switching. In the mean time, got too much coding to do to pay attention.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

