Hi David,
> > I tried to branch/tag a revision of code that we released, and when
I
> > came back to do another release of the same code base, I did an
update
> > on the directory. Turns out, that the external directories had some
> > code that was changed/updated which had a bug that broke the "old"
code.
> >
> > So, in writing this out. I wasn't tagging the external code, and
that
> > my other code base should only use the tagged (e.g.: stable code).
Am I
> > on the right track here?
The script svncopy.pl.in in the contrib/client-side directory of the
subversion repository attempts to solve this problem. If you run
svncopy.pl --tag it will update all externals in the copied directories
to the current revision. If you run svncopy.pl --branch it will update
all externals which point to destinations within the copy source to
point to the corresponding destination within the copy target. (I.e. if
you copy foo/bar and foo/baz and foo/baz points to foo/bar it will
update it. If it points to fu/ba instead, it will leave it alone. Not
completely intuitive - you need to remember to branch at a high enough
level to include everything.)
Cheers,
Ian Brockbank
Applications Software Team Leader
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Dec 6 10:52:16 2005