If you're using git and have a component or chunk of SVN* checked out
using the "git svn clone -s" approach [1], you can use this to switch to
the new branch:
git svn fetch # get latest branches and commits
git checkout -b local/devstudio-4.0.x devstudio-4.0.x # use new branch
git svn info # verify now working in branch
[1]
http://justaddwater.dk/2009/03/09/using-git-for-svn-repositories-workflow/
* - JBoss Tools repo is too big for my machine to do a `git svn clone`
(runs out of memory), but devstudio can be done, or individual
components in JBT can be done
(And if you're not using git, then you can ignore ALL of the above.)
On 01/24/2011 01:06 PM, Max Rydahl Andersen wrote:
Please note that this means you cannot commit to the CR1 branch
anymore - if you already have it checked out then you should be able to use svn switch for
a fast "update".
/max
> FYI, I have done the following per Max's instruction:
you forgot the part that said: mail about it *before* the change ;)
> # tag CR1 branch for CR1 release
> svn copy
http://svn.jboss.org/repos/devstudio/branches/devstudio-4.0.0.CR1/
http://svn.jboss.org/repos/devstudio/tags/devstudio-4.0.0.CR1/
> svn copy
http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.CR1/
http://svn.jboss.org/repos/jbosstools/tags/jbosstools-3.2.0.CR1/
>
> # rename CR1 branch to .x
> svn move
http://svn.jboss.org/repos/devstudio/branches/devstudio-4.0.0.CR1/
http://svn.jboss.org/repos/devstudio/branches/devstudio-4.0.x
> svn move
http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.CR1/
http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools& Dev Studio
> Release Engineer :: Eclipse Modeling& Dash Athena
>
http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash Athena
http://nick.divbyzero.com