<?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: Adding a New Rails Project under Subversion</title>
	<atom:link href="http://jamescrisp.org/2007/07/01/adding-a-new-rails-project-under-subversion/feed/" rel="self" type="application/rss+xml" />
	<link>http://jamescrisp.org/2007/07/01/adding-a-new-rails-project-under-subversion/</link>
	<description>C#, .NET, Ruby, Rails, book reviews, mind hacks, Wing Chun and the occasional personal bit.</description>
	<lastBuildDate>Sun, 15 Jan 2012 14:28:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Josh G</title>
		<link>http://jamescrisp.org/2007/07/01/adding-a-new-rails-project-under-subversion/#comment-80</link>
		<dc:creator>Josh G</dc:creator>
		<pubDate>Mon, 02 Jul 2007 06:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://jamescrisp.org/wordpress/?p=63#comment-80</guid>
		<description>Nice - also have a look at http://wiki.rubyonrails.org/rails/pages/HowtoUseRailsWithSubversion for tips and links to other similar tutorials.&lt;br/&gt;&lt;br/&gt;On a side note, when you have large projects or those with lots of repository activity (like most Agile projects do), it&#039;s often good to have a distinct repository per project, as there&#039;s less effort in processing what&#039;s changed between repository version numbers and whether it applies to your subtree. Anyway, it&#039;s easy enough to split/merge repositories with svnadmin.</description>
		<content:encoded><![CDATA[<p>Nice - also have a look at <a href="http://wiki.rubyonrails.org/rails/pages/HowtoUseRailsWithSubversion" rel="nofollow">http://wiki.rubyonrails.org/rails/pages/HowtoUseRailsWithSubversion</a> for tips and links to other similar tutorials.</p>
<p>On a side note, when you have large projects or those with lots of repository activity (like most Agile projects do), it's often good to have a distinct repository per project, as there's less effort in processing what's changed between repository version numbers and whether it applies to your subtree. Anyway, it's easy enough to split/merge repositories with svnadmin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

