<?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"
	>
<channel>
	<title>Comments on: Converting From CVS to Subversion</title>
	<atom:link href="http://www.symphonious.net/2005/08/06/converting-from-cvs-to-subversion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2005/08/06/converting-from-cvs-to-subversion/</link>
	<description>Living in a state of accord.</description>
	<pubDate>Thu, 04 Dec 2008 07:40:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Milo</title>
		<link>http://www.symphonious.net/2005/08/06/converting-from-cvs-to-subversion/#comment-7285</link>
		<dc:creator>Milo</dc:creator>
		<pubDate>Thu, 11 Aug 2005 01:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2005/08/06/converting-from-cvs-to-subversion/#comment-7285</guid>
		<description>We have been running subversion fine for ages here, but recently (inspired by one of your earlier posts actually), we decided to set up an RSS feed of the commit log via trac wiki.  Since then we've had a to recover the db multiple times as we cannot for the life of us get Apache to play nice and keep subversion from getting 'wedged' (Problem with berklyDB backing, apparently wouldn't happen if we used flat file backing).  No serious damage, but damn annoying, especially if no one with access is around to fix it when you need repository access.  Something you may want to be aware of.
</description>
		<content:encoded><![CDATA[<p>We have been running subversion fine for ages here, but recently (inspired by one of your earlier posts actually), we decided to set up an RSS feed of the commit log via trac wiki.  Since then we&#8217;ve had a to recover the db multiple times as we cannot for the life of us get Apache to play nice and keep subversion from getting &#8216;wedged&#8217; (Problem with berklyDB backing, apparently wouldn&#8217;t happen if we used flat file backing).  No serious damage, but damn annoying, especially if no one with access is around to fix it when you need repository access.  Something you may want to be aware of.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
