<?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: Upgrading wordpress with git</title>
	<atom:link href="http://blog.affien.com/archives/2007/06/07/upgrading-wordpress-with-git/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.affien.com/archives/2007/06/07/upgrading-wordpress-with-git/</link>
	<description>A few thoughts</description>
	<lastBuildDate>Sun, 31 May 2009 12:07:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bas</title>
		<link>http://blog.affien.com/archives/2007/06/07/upgrading-wordpress-with-git/comment-page-1/#comment-169319</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Thu, 01 May 2008 22:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.w-nz.com/archives/2007/06/07/upgrading-wordpress-with-git/#comment-169319</guid>
		<description>You&#039;re probably right.  Obviously you indeed want to check for stray files.  Some might be usefull to keep around like uploaded images and alike.  A look at &lt;code&gt;git status&lt;/code&gt; is always helpful.

If you want to clean untracked files from your repo then &lt;code&gt;git clean&lt;/code&gt; (&lt;code&gt;-f&lt;/code&gt;) is your friend.</description>
		<content:encoded><![CDATA[<p>You&#8217;re probably right.  Obviously you indeed want to check for stray files.  Some might be usefull to keep around like uploaded images and alike.  A look at <code>git status</code> is always helpful.</p>
<p>If you want to clean untracked files from your repo then <code>git clean</code> (<code>-f</code>) is your friend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Addleman</title>
		<link>http://blog.affien.com/archives/2007/06/07/upgrading-wordpress-with-git/comment-page-1/#comment-169108</link>
		<dc:creator>Jonathan Addleman</dc:creator>
		<pubDate>Tue, 29 Apr 2008 22:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.w-nz.com/archives/2007/06/07/upgrading-wordpress-with-git/#comment-169108</guid>
		<description>I know this post is a little out of date now, but looks like it should still work with current versions of git and wordpress. One exception is that you&#039;ll need to use &quot;git checkout -b tmp HEAD^&quot; instead of doing the checkout and the branch in two steps. I don&#039;t know if that ever worked in two commands like you used there... It didn&#039;t for me though!

The other issue I see is that if a new version of wordpress removed files that were present in the old version, the steps you describe won&#039;t get rid of the old files. To prevent that, I think that deleting all the files before copying the new version into the tmp dir should work.</description>
		<content:encoded><![CDATA[<p>I know this post is a little out of date now, but looks like it should still work with current versions of git and wordpress. One exception is that you&#8217;ll need to use &#8220;git checkout -b tmp HEAD^&#8221; instead of doing the checkout and the branch in two steps. I don&#8217;t know if that ever worked in two commands like you used there&#8230; It didn&#8217;t for me though!</p>
<p>The other issue I see is that if a new version of wordpress removed files that were present in the old version, the steps you describe won&#8217;t get rid of the old files. To prevent that, I think that deleting all the files before copying the new version into the tmp dir should work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
