Comments on: Using Subversion with WordPress – Part 2: Maintaining Vendor Branches and Upgrading WP Core Files

By: gib

gib — Mon, 08 Feb 2010 07:34:55 +0000

fully agree with tunesmith,
what about a svn switch automattic/tags/2.9.1.1
inside vendor/wordpress/current ?
anyway very useful articles, thanks a lot !

By: tunesmith

tunesmith — Sat, 07 Nov 2009 02:28:38 +0000

It would be nicer to just pull over the wordpress update through a svn update, and then merge it into one’s own workspace. Is this possible? It just seems that that export/delete/copy process is something that subversion should be able to do.

The alternative is externals, but it requires wordpress being in its own directory, and wp-content screws that up.

By: elran

elran — Sun, 20 Apr 2008 18:09:03 +0000

no they won’t.

if you followed steps #5 and #6 from Part 1 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.

By: mike

mike — Sat, 19 Apr 2008 22:24:48 +0000

what about all your custom plugins, themes, etc? those will be overwritten with these commands…