<?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: git by example &#8211; upgrade wordpress like a ninja</title>
	<atom:link href="http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/</link>
	<description>A blog about nothing</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:14:03 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Golgo Com Plexsho</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-152865</link>
		<dc:creator>Golgo Com Plexsho</dc:creator>
		<pubDate>Mon, 18 Oct 2010 21:17:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-152865</guid>
		<description>haha, that is the best tutorial for beginners, that´s what I was thinking. Finally git made easy. BUT then the comment by Sharpy - and suddenly, after reading all the page, everything breaks together to pieces. I hate this complexity of git. Everybody seems to use it in a different way and nobody really seems to really understand, what happens...
if you have the same feeling: I feel that mercurial is much more easy to work with, there is one way to do it and not one million different ways.</description>
		<content:encoded><![CDATA[<p>haha, that is the best tutorial for beginners, that´s what I was thinking. Finally git made easy. BUT then the comment by Sharpy &#8211; and suddenly, after reading all the page, everything breaks together to pieces. I hate this complexity of git. Everybody seems to use it in a different way and nobody really seems to really understand, what happens&#8230;<br />
if you have the same feeling: I feel that mercurial is much more easy to work with, there is one way to do it and not one million different ways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: numerodix</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-120228</link>
		<dc:creator>numerodix</dc:creator>
		<pubDate>Fri, 11 Dec 2009 15:53:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-120228</guid>
		<description>Perhaps you&#039;re right, maybe I should have done that.</description>
		<content:encoded><![CDATA[<p>Perhaps you&#8217;re right, maybe I should have done that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sharp</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-120095</link>
		<dc:creator>Adam Sharp</dc:creator>
		<pubDate>Wed, 09 Dec 2009 23:25:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-120095</guid>
		<description>Is there a particular reason that you chose rebasing over merging? From what I&#039;ve read so far (I&#039;ve been using git for a little while now) it would achieve the same thing and give you a more accurate history to do the following when upgrading:

- Make changes on the &#039;mine&#039; branch
- Checkout &#039;master&#039; and perform the WP upgrade
- Checkout &#039;mine&#039; once more
- Merger &#039;master&#039; into &#039;mine&#039;
- Resolve merge conflicts if necessary

This still leaves &#039;master&#039; intact, only containing the upstream WP code, but gives all the benefit of the upgrade on the &#039;mine&#039; branch. Also because you have preserved your commit history rather than rebasing, you can still revert to the state prior to the merge with no worries.

What do you think?

—Sharpy</description>
		<content:encoded><![CDATA[<p>Is there a particular reason that you chose rebasing over merging? From what I&#8217;ve read so far (I&#8217;ve been using git for a little while now) it would achieve the same thing and give you a more accurate history to do the following when upgrading:</p>
<p>- Make changes on the &#8216;mine&#8217; branch<br />
- Checkout &#8216;master&#8217; and perform the WP upgrade<br />
- Checkout &#8216;mine&#8217; once more<br />
- Merger &#8216;master&#8217; into &#8216;mine&#8217;<br />
- Resolve merge conflicts if necessary</p>
<p>This still leaves &#8216;master&#8217; intact, only containing the upstream WP code, but gives all the benefit of the upgrade on the &#8216;mine&#8217; branch. Also because you have preserved your commit history rather than rebasing, you can still revert to the state prior to the merge with no worries.</p>
<p>What do you think?</p>
<p>—Sharpy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Robinson</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-100121</link>
		<dc:creator>Mark Robinson</dc:creator>
		<pubDate>Sun, 12 Apr 2009 19:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-100121</guid>
		<description>Hi, I&#039;ve been trying to work this out on my own for ages - thanks so much for documenting it in a simple to understand way.</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;ve been trying to work this out on my own for ages &#8211; thanks so much for documenting it in a simple to understand way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Praveen</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-76791</link>
		<dc:creator>Praveen</dc:creator>
		<pubDate>Sun, 12 Oct 2008 20:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-76791</guid>
		<description>Hey, Thanks a lot for the detailed writeup. really appreciate the effort. 
The post is very simple, self explanatory, to the point and covers all sections. 

Cheers! Keep up the great work.</description>
		<content:encoded><![CDATA[<p>Hey, Thanks a lot for the detailed writeup. really appreciate the effort.<br />
The post is very simple, self explanatory, to the point and covers all sections. </p>
<p>Cheers! Keep up the great work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Git by Example - Upgrade Wordpress Like a Ninja &#124; WebLaunches</title>
		<link>http://www.matusiak.eu/numerodix/blog/index.php/2008/09/21/git-by-example-keeping-wordpress-up-to-date/#comment-74996</link>
		<dc:creator>Git by Example - Upgrade Wordpress Like a Ninja &#124; WebLaunches</dc:creator>
		<pubDate>Mon, 22 Sep 2008 19:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.matusiak.eu/numerodix/blog/?p=1352#comment-74996</guid>
		<description>[...] In fact, with git you can keep track of what changes you have made and have access to them&#8230;read more &#124; digg [...]</description>
		<content:encoded><![CDATA[<p>[...] In fact, with git you can keep track of what changes you have made and have access to them&#8230;read more | digg [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

