"Lars Heineken" <lars.heineken@diasemi.com> wrote on 12/16/2005 04:20:07
AM:
> I just had a call from one of my collegues who is using Subclipse to
> manage his program releases. He used to give the project folder a
> different
> name when releasing a program: "test" -> "test_1.0".
> As far as I can remember, the Branch/Tag-command used to be a multi step
> operation that offered the option to either use the project's name as
> final
> destination folder (eg. "test") oder provide a different project name
> ("test_1.0").
> On the current implementation of the Branch/Tag command this has been
> changed
> to a one click procedure.
> I'm curious why this change has been made as I promised to give my
> collegue
> an reasonable answer :-)
I do not really know what you are talking about. Nothing has really been
changed in this area. Perhaps you are being tripped up by the semantics
of the Subversion copy operation? If the target of your copy already
exists, then Subversion copies the folder into the target. If the target
does not exist, then it creates the target and copies the contents of the
folder into the target. The net result is that typically you want to
allow the copy option to create the target folder. It will then use the
name you provided and copy the contents into that name.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Sat Dec 17 00:59:31 2005