[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Subversion Vision and Roadmap Proposal

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Fri, 9 Apr 2010 18:26:47 -0400

> The trick is to use the --stop-on-copy (to stop at branch point)
> -v (to show patsh) options of the svn log command:
>
> $ svn log --stop-on-copy -v .
> ------------------------------------------------------------------------
> r3 | stsp | 2010-04-09 22:25:24 +0100 (Fri, 09 Apr 2010) | 1 line
> Changed paths:
> M /branch/beta
>
> a commit on the branch
> ------------------------------------------------------------------------
> r2 | stsp | 2010-04-09 22:24:57 +0100 (Fri, 09 Apr 2010) | 1 line
> Changed paths:
> A /branch (from /trunk:1)
>
> creating branch
> ------------------------------------------------------------------------
> $
>
> So /branch was copied from /trunk_at_1.
>
> > Branch is similar. If I want to set to the point on trunk at which
> > branches/2.0 was branched, how do I do this?
> > In GIT, it's just "git checkout master", "git reset --hard
> branches/2.0".
>
> Find the revision at which the branch was created using
> "svn log" as above. Then copy the old version of the branch
> on top of the current version:
>
> svn rm ^/branch
> svn copy ^/trunk_at_12345 ^/branch

Wouldn't this cause a folder/path already exists error?

BOb
Received on 2010-04-10 00:25:55 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.