<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Using Subversion with WordPress - Part 2: Maintaining Vendor Branches and Upgrading WP Core Files</title>
	<link>http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-2-maintaining-vendor-branches-and-upgrading-wp-core-files/</link>
	<description>Techblog is collection of articles covering a wide variety of tech related topics including: Linux, Microsoft, code, design, wordpress, security, new media and more. Site updated regularly; search by category, title, date, or tag.</description>
	<pubDate>Sun, 23 Nov 2008 16:03:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: elran</title>
		<link>http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-2-maintaining-vendor-branches-and-upgrading-wp-core-files/#comment-34697</link>
		<dc:creator>elran</dc:creator>
		<pubDate>Sun, 20 Apr 2008 18:09:03 +0000</pubDate>
		<guid>http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-2-maintaining-vendor-branches-and-upgrading-wp-core-files/#comment-34697</guid>
		<description>no they won't.

if you followed steps #5 and #6 from &lt;a href="http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-1-creating-vendor-branches-and-integrating-your-existing-code/" rel="nofollow"&gt;Part 1&lt;/a&gt; and prepared your files correctly - all your custom plugins and themes should already be under version control at this point.

furthermore, you would be merging only the differences between 2 versions of WordPress (an upgrade of core files) - this has nothing to do with your custom plugins and themes.</description>
		<content:encoded><![CDATA[<p>no they won&#8217;t.</p>
<p>if you followed steps #5 and #6 from <a href="http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-1-creating-vendor-branches-and-integrating-your-existing-code/" rel="nofollow">Part 1</a> and prepared your files correctly - all your custom plugins and themes should already be under version control at this point.</p>
<p>furthermore, you would be merging only the differences between 2 versions of WordPress (an upgrade of core files) - this has nothing to do with your custom plugins and themes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-2-maintaining-vendor-branches-and-upgrading-wp-core-files/#comment-34696</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Sat, 19 Apr 2008 22:24:48 +0000</pubDate>
		<guid>http://techblog.touchbasic.com/html/using-subversion-with-wordpress-part-2-maintaining-vendor-branches-and-upgrading-wp-core-files/#comment-34696</guid>
		<description>what about all your custom plugins, themes, etc? those will be overwritten with these commands...</description>
		<content:encoded><![CDATA[<p>what about all your custom plugins, themes, etc? those will be overwritten with these commands&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
