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

Re: [Subclipse-users] Noobie: Convert working copy to new branch

From: Gunnar Wagenknecht <gunnar_at_wagenknecht.org>
Date: 2006-08-24 14:56:01 CEST

Mark Phippard wrote:
> Why is this "better" when it is so many steps? It separates the creation
> of the branch from the commit of your changes. This makes it easier to
> create a patch with your changes, or to later merge them back to trunk.

Mark, do you have a recommendation of how to handle branching/tagging of
multiple projects in the same repository? Right now I tag them outside
of Eclipse by selecting the parent "trunk" folder.

I also noticed that tagging/branching fails in Eclipse if the folder
hierarchy is to deep because some folders do not exist yet.

Project: my.eclipse.plugin
Trunk: .../trunk/plugins/my.eclipse.plugin/
Tag: .../tags/MYTAG/plugins/my.eclipse.plugin/

Usually at tagging time only the folder "tags" exists. Thus,
"MYTAG/plugins" has to be created. Could Subclipse do this automatically
instead of failing the tag operation?

Another suggestion. If I select multiple projects, could Subclipse
detect a common repository URL structure and support tagging them all at

ProjectA .../trunk/plugins/my.eclipse.plugin.a/
ProjectB .../trunk/plugins/my.eclipse.plugin.b/
ProjectF .../trunk/features/my.eclipse.feature/

Common repository URL would be ".../trunk". The Tag/Branch dialog would
ask me for the new "parent" URL, eg. ".../tags/MYTAG" and then Subclipse
would tag them accordingly, either as one atomic operation (if supported
by Subversion) or my several operations.

Cu, Gunnar

Gunnar Wagenknecht
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Aug 24 15:13:04 2006

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.