[wp-hackers] Switching from SVN

Jacob Santos wordpress at santosj.name
Sat Dec 11 05:56:23 UTC 2010

On Fri, Dec 10, 2010 at 7:23 AM, Mike Schinkel
<mikeschinkel at newclarity.net>wrote:

> On Dec 10, 2010, at 8:16 AM, scribu wrote:
> >
> > The current release is under tags/3.0.3.
> >
> > The stable branch is in branches/3.0.
> >
> > At the moment, the 3.0 branch is identical to the 3.0.3 tag, because
> there
> > haven't been any commits made yet, but that's not always the case.
> So with SVN I still have the issue I described; assuming I don't want to
> break my project by installing not released code I still have to set up
> another install in order to generate a patch, right?

I wonder if something changed during the time I created patches for both the
trunk and branch. Usually, I would create a patch against trunk. SVN switch
to the branch 3.0 or branches/x.x and then apply the patch I created against
trunk to it. If it applies then I'm ready to go, if it does not, then I
modify the code for the branch and create a new patch for that version.

Mike Little explanation seems to leave off the part where you create a patch
for trunk. However, I'm tired, so I apologize if I'm a bit insane.

Jacob Santos

More information about the wp-hackers mailing list