Comments on: When svn up does not work (Wordpress subversion)

By: wordpress 2.5 and subversion by Rich Zygler at boringguys.com

wordpress 2.5 and subversion by Rich Zygler at boringguys.com — Sat, 02 Aug 2008 12:55:24 +0000

[...] For some reason, performing an svn update on the external repository http://svn.automattic.com/wordpress/trunk/ does absolutely nothing.Â This is pretty baffling behavior.Â Same wordpress and subversion issue also mentioned here. [...]

By: jez

jez — Tue, 10 Jun 2008 05:53:04 +0000

@Jonathan: thanks for the hint, I will definitely bash that into putty later on!

By: Jonathan

Jonathan — Mon, 09 Jun 2008 18:08:37 +0000

There’s a happy medium:
svn sw http://automattic.com/wordpress/branches/2.5/ .
Today that would give you v2.5.2 alpha. And the only svn sw you’d have to do is when the 2.6 branch is ready enough for you.

By: jez

jez — Fri, 02 May 2008 14:52:01 +0000

@Jeremy: thanks a lot for your detailed comment! I do now understand why I have to use svn sw .. , still it is annoying :) Using the bleeding edge release is one possibility, as stated by you, however this comes at certain caveats…

By: Jeremy

Jeremy — Fri, 02 May 2008 14:49:01 +0000

You have to use the sw command because your svn is tied to a particular branch. For instance, at the time you posted, your blog’s svn was set to 2.3.3 and you will need to keep switching to stay updated. “svn update” only updates your stuff to the branch that you’re on. You /could/ sw to wordpress’s trunk, but then you risk breakage and difficulties (in exchange for earlier access to new features).