<?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: Ruby SVN Hooks</title>
	<atom:link href="http://theblogthatnoonereads.davegrijalva.com/2007/11/25/ruby-svn-hooks/feed/" rel="self" type="application/rss+xml" />
	<link>http://theblogthatnoonereads.davegrijalva.com/2007/11/25/ruby-svn-hooks/</link>
	<description>Except for you.  You read it.</description>
	<lastBuildDate>Thu, 21 Jul 2011 18:38:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3-aortic-dissection</generator>
	<item>
		<title>By: The Blog that Noone Reads &#187; Blog Archive &#187; Keeping and Eye on SVN with svn_hooks</title>
		<link>http://theblogthatnoonereads.davegrijalva.com/2007/11/25/ruby-svn-hooks/comment-page-1/#comment-10888</link>
		<dc:creator>The Blog that Noone Reads &#187; Blog Archive &#187; Keeping and Eye on SVN with svn_hooks</dc:creator>
		<pubDate>Mon, 26 Nov 2007 20:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://theblogthatnoonereads.tunasoft.com/ruby-svn-hooks/#comment-10888</guid>
		<description>[...] I&#8217;ve been working on a new ruby gem to make it easier to write scripts for handling subversion events. The idea is to allow you to separate your code into files based on project or task, rather than based on event. There are some simple methods available for filtering based on event type or area of the repository that&#8217;s been touched. Also made available are all of the details of the last event, including touched files (and their state flags), author, date, and comment. You can get the package here. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve been working on a new ruby gem to make it easier to write scripts for handling subversion events. The idea is to allow you to separate your code into files based on project or task, rather than based on event. There are some simple methods available for filtering based on event type or area of the repository that&#8217;s been touched. Also made available are all of the details of the last event, including touched files (and their state flags), author, date, and comment. You can get the package here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

