[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: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-07-11 17:40:42 CEST

On 7/11/06, Jaap Vermeulen <jaap@skyscape.com> wrote:
>
> Hi again.
>
> It's too bad there was only a single response to my original message
> outlining the problem we run into. This response stated:
>
> > 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.
>
> This, IMHO, shows that the problem I described is not clearly understood.
> Let me reiterate that it is impossible to have a common root due to the
> hierarchical nature of SVN. If we had a common root, and we would run a
> checkout, we would be checking out gigabytes of information for hundreds of
> versions for the 300+ products I mentioned.

What if your common root was a non-recursive checkout (only get that
one directory), then update the needed directories as needed (again,
always working non-recusrive on that common root)?

> The whole concept of tying the bugtraq properties to a specific point in the
> hierarchy because you assume that that point of the hierarchy is always
> included is a fallacy IMHO. I would rather see a repository-wide directive
> that is in effect for all working copies, regardless of where in the
> hierarchy they were checked out from.

Would a pre-commit hook script, rejecting commits that don't meet your
buqtraq property requirements, work?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jul 11 17:40:53 2006

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