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

Recursive properties should apply to newly added directories?

From: Peter Mounce <petermounce_at_iml.co.uk>
Date: 2005-01-25 10:47:55 CET

I have an svn repository (based on v1.1.3, accessed with T-SVN 1.1.3) which
has a layout, say

trunk/
        projectA/
                module1/
                module2/
        projectB/

etc

On trunk, I have recursively set svn:ignore to ignore compiler output files.

If I add a directory, /trunk/projectA/module3, the svn:ignore does not get
parsed, and files I want ignored (from module3; say I've compiled already
and there's fluff in there) get added to the list of files to be added (I'm
using T-SVN; I get a dialogue box asking which files in the list I wish to
add).

The new directory does not inherit the properties that a previous recursive
set operation would have set on it if the directory had been there earlier
(before the recursive set).

Should it have done that (made the new directory have the same properties as
the parent directory) intrinsically (via some knowledge that properties had
been set recursively earlier - I doubt that's stored, though, right?)? Or
should this be an option presented to the user by whichever client is being
used?

I tried to think of an instance where I would _not_ want properties to be
inherited by newly added directories, but failed. It's only
one-coffee-o'clock, however.

Not really sure if this is an issue for SVN or T-SVN.

Regards
Peter Mounce
 
IML Ltd
Tel: (01428) 727476
Fax: (01428) 727011
Web: www.iml.co.uk <http://www.iml.co.uk/>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 25 10:51:57 2005

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

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