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

Re: Feature request: change the way you set TSVN bugtraq: properties

From: Sven Brueggemann <SBrueggemann_at_gmx.net>
Date: 2006-04-25 23:05:31 CEST

Hello,

> We worked around some peculiarities of Subversion and have our own release
> tools on top of Subversion (branching/labeling/releasing). One issue I
> can't find a reasonable solution for is to make changes to the bugtraq:
> properties for these 300+ products (or having to add them every time we
> add a new product). Because these products start deeper down the hierarchy,
> there is no common root from which to retrieve these properties, and
> therefore changes have to be made at least in 300+ places, often more.

TSVN fetches the bugtraq properties from the working copy,
not the repository. So although it is not officially recommended,
you can work with a "common root" checked out "above" your working
copies.

Example:

Have a folder CommonRoot in your repository and apply the bugtraq-properties
to it.

Check it out to - say - c:\CommonRoot.

In C:\CommonRoot you can create subdirectories to check out your
projects to: C:\CommonRoot\Project1, C:\CommonRoot\Project2.

Project1 and Project2 are called "nested working copies" in this case.
As Stefan said a few mails ago, it is not recommended to layout your
projects like this, but TSVN handles this very well and I have made
good experiences with that.

(I did it this way because I had to deal with a "legacy" project layout
and noticed later, that it's just fine for common property-bound policies
and the bugtraq-features).

Kind regards

Sven

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Apr 25 23:05:27 2006

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

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