<?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: &#8220;Warning: &#8216;post-commit&#8217; hook failed with error output:&#8221;</title>
	<atom:link href="http://blogs.gnome.org/tthurman/2008/05/30/post-commit/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/tthurman/2008/05/30/post-commit/</link>
	<description>Thomas Thurman does not like cold meals because of broken applications.</description>
	<pubDate>Thu, 20 Nov 2008 09:50:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: James Henstridge</title>
		<link>http://blogs.gnome.org/tthurman/2008/05/30/post-commit/#comment-122</link>
		<dc:creator>James Henstridge</dc:creator>
		<pubDate>Tue, 03 Jun 2008 02:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/tthurman/2008/05/30/post-commit/#comment-122</guid>
		<description>It also happens if it is a script that is executable by you but not readable, as I found with one project I worked with.

The outcome in this situation is that the commit has succeeded but your working tree is still pointing at the old revisiion.  A simple "svn update" seems enough to get you going again (although the post-commit won't have run).</description>
		<content:encoded><![CDATA[<p>It also happens if it is a script that is executable by you but not readable, as I found with one project I worked with.</p>
<p>The outcome in this situation is that the commit has succeeded but your working tree is still pointing at the old revisiion.  A simple &#8220;svn update&#8221; seems enough to get you going again (although the post-commit won&#8217;t have run).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
