[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: Jaap Vermeulen <jaap_at_skyscape.com>
Date: 2006-07-11 22:03:46 CEST

Andy wrote (thanks Andy):

> 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 non-recursive checkouts were fairly buggy in the beginning when we
started several years ago. And even if it works perfectly now, it would be
pretty clumsy and cumbersome to have to check out a tree by using
non-recursive checkouts. Finally, I don't know what would happen trying to
commit such a tree, but I don't think it would work.

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

Sure, it could check for it, but it's the more than 300+ existing products
for which I would like to establish the linkage. The bug numbers are
already in the log messages; they simply don't link yet because of the
missing attributes.

And that brings me to the other aspect that would be solved. Currently, if
you're outside a working copy and looking directly into the repository,
these bug numbers don't link *because* it's only linked through directory
attributes on working copies. Why? Allow this linkage to be specified
globally or per-repository. It makes reasonable sense, and you could still
override it using per-directory working copy attributes.

Features like this work great on small repositories, but on this 5.25 GB
repository with many directory levels, and many independent "views", it
doesn't really work any more.



To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Jul 11 22:16:59 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.