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

RE: Do not copy Bugtraq properties for new folders

From: Bob Archer <Bob.Archer_at_amsi.com>
Date: Tue, 27 Aug 2013 13:44:13 +0000

> Hi!
> On 23 August 2013 17:42, Ben Fritz <fritzophrenic_at_gmail.com> wrote:
> On Fri, Aug 23, 2013 at 6:57 AM, Nicolai Scheer <scope_at_planetavent.de>
> wrote:
> > Hi!
> >
> > We use a few bugtraq properties set on the root of our projects to
> > make it easier for our developers to add a ticket no. to their commits.
> >
> > Now, when I add a new folder to the working copy, (i.e. creating it
> > and afterwards choose "add" in the tsvn context menu) the bugtraq
> > properties are copied to the new folder.
> >
> > Is there any way to prevent this? Tsvn searches the WC upwards for
> > these properties, so I don't see a need to have them on subfolders.
> >
> And do you know for a fact that nobody will ever check out a working copy of
> only that subdirectory within your project? That's the need for the behavior; so
> you can get that property in your working copy no matter which directory
> under the project you use for your working copy root.
>  Yes, I do know that for a fact. That's a convention on the one hand, and a
> technical requirement (e.g. unit tests) on the other.
> To my mind, just copying the properties is very problematic. What if I alter the
> properties at the project root? I'd have to make sure, that each and every
> folder is changed, too. I know that could be done with recursively deleting and
> re-adding the props, so it would be fast at least.
> But to my mind, Tsvn should not alter my working copy in any way without me
> being able to deactivate this behaviour.
> Of course, the project properties are somehow special, because they are
> "pseudo-inherited", and that's the reason I would not expect that they are
> copied on newly created folders.
> Anyway, there are different tastes out there, I did not want to discuss if I find
> this feature useful in the first place :) I'd just like to know, if it can be
> deactivated...
> Greetings
> Nico

I think with the new inheritable properties TSVN would be able to modify its behavior to not need the property on every folder. Perhaps they will create a change request for this.

However, when you add the folder, you can edit the properties before you commit it. Is the property causing you an issue for some reason? What is the use case for it not being there? I'm sure the devs would want to know that before making such a low level change.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-08-27 15:44:20 CEST

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.