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

[Subclipse-users] Best way to tag multiple projects

From: Paul Glezen <pglezen_at_us.ibm.com>
Date: 2007-01-25 18:32:35 CET

Thanks, Mark. That explains why I sometimes saw one behavior, and other
times saw another. I thought I was going crazy. (Actually, I am going
crazy. It just turns out to be unrelated to this.)

>
>
> My SVN repository has the traditional SVN structure of
>
> repo
> |
> |--tags
> | |
> | |--rel-1.0
> |--trunk
> | |
> | |--proj1
> | |--proj2
> ...
> | |--projN
>
> What is the most efficient way to tag all the projects from the HEAD of
> the trunk to rel-1.0? I've been going to each individual project and
> selecting Team -> Branch/Tag and selectiong "repo/targs/rel-1.0" for my
> To-URL. But this becomes onerous as N increases. I thought perhaps I
could
> use the repository view and select "trunk" as my from-URL. But then it
> creates a "trunk" subdirectory of the tag, which I don't really want. Is
> there a better way?
>
Doing it from the repository browser was the way to go. The reason you got
the trunk folder must have been that the rel-1.0 folder already existed and
that is how Subversion copy works in that scenario. The key would be to
allow the create tag (copy) feature to create the rel-1.0 folder as part of
the process, and then it would do what you want.

Paul
Received on Thu Jan 25 18:37:18 2007

This is an archived mail posted to the Subclipse Users mailing list.

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