<?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: 4 Unusual uses for Subversion</title>
	<atom:link href="http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/feed/" rel="self" type="application/rss+xml" />
	<link>http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/</link>
	<description>May The Source Be With You.</description>
	<pubDate>Tue, 06 Jan 2009 02:51:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom Verhoeff</title>
		<link>http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/comment-page-1/#comment-10601</link>
		<dc:creator>Tom Verhoeff</dc:creator>
		<pubDate>Wed, 03 Sep 2008 22:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://beta.ariejan.net/?p=86#comment-10601</guid>
		<description>Concerning the use of Subversion as Content Management System (CMS for websites), one should keep in mind that Subversion does not keep track of file permissions.

There are some ways to deal with that (svn wrappers, a special svn version, or separate permission-tweaking scripts on the web server), but none of them is really convenient, IMHO.</description>
		<content:encoded><![CDATA[<p>Concerning the use of Subversion as Content Management System (CMS for websites), one should keep in mind that Subversion does not keep track of file permissions.</p>
<p>There are some ways to deal with that (svn wrappers, a special svn version, or separate permission-tweaking scripts on the web server), but none of them is really convenient, IMHO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/comment-page-1/#comment-10546</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 23 Jun 2008 14:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://beta.ariejan.net/?p=86#comment-10546</guid>
		<description>Are there any example of people using Subversion for media heavy projects such as a DVD, film or computer game assets?</description>
		<content:encoded><![CDATA[<p>Are there any example of people using Subversion for media heavy projects such as a DVD, film or computer game assets?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 4 Unusual uses for Subversion &#171; codedigestion:shree mulay</title>
		<link>http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/comment-page-1/#comment-213</link>
		<dc:creator>4 Unusual uses for Subversion &#171; codedigestion:shree mulay</dc:creator>
		<pubDate>Tue, 10 Jul 2007 19:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://beta.ariejan.net/?p=86#comment-213</guid>
		<description>[...] read more &#124; digg story [...]</description>
		<content:encoded><![CDATA[<p>[...] read more | digg story [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stian Haklev</title>
		<link>http://ariejan.net/2007/02/26/4-unusual-uses-for-subversion/comment-page-1/#comment-214</link>
		<dc:creator>Stian Haklev</dc:creator>
		<pubDate>Tue, 17 Apr 2007 07:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://beta.ariejan.net/?p=86#comment-214</guid>
		<description>You forgot one of the best ones, keeping /etc in svn! I've started doing this on all my servers now and it's great. Before you do apt-get install apache, you commit /etc, then you install apache, and you do svn add . --force, and commit again. You have a list of every file added, every file modified etc, and you can easily roll back at any time. Awesome to get a log of every config file, if you ever have problems etc.

I'd love to see a solution where this was tied automatically to apt-get so it could autocommit or something, but so far I just do it whenever I remember. (If you remember to commit at a clean install, it's also a great way of documenting all the changes you 've made, for someone taking over).

A Google SoC project this summer looks at making a nice graphical tool to put your home directory in SVN.</description>
		<content:encoded><![CDATA[<p>You forgot one of the best ones, keeping /etc in svn! I&#8217;ve started doing this on all my servers now and it&#8217;s great. Before you do apt-get install apache, you commit /etc, then you install apache, and you do svn add . &#8211;force, and commit again. You have a list of every file added, every file modified etc, and you can easily roll back at any time. Awesome to get a log of every config file, if you ever have problems etc.</p>
<p>I&#8217;d love to see a solution where this was tied automatically to apt-get so it could autocommit or something, but so far I just do it whenever I remember. (If you remember to commit at a clean install, it&#8217;s also a great way of documenting all the changes you &#8216;ve made, for someone taking over).</p>
<p>A Google SoC project this summer looks at making a nice graphical tool to put your home directory in SVN.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
