Sorry to revive a thread from 3 weeks ago, but I had a thought. These things do not happen to me every day, you know!
[Stefan Sperling] > When adding a recursive directory tree, we only heed the global ignores > list. Recall that the svn:ignore property is not inherited. > Subversion is adding the directory to version control, and immediately > proceeds to read the global ignores list, and the (obviously non-existent) > svn:ignore property of the new directory > (see subversion/libsvn_client/add.c:add_dir_recursive()). This makes me wonder if 'svn add' / 'svn mkdir' should explicitly copy svn:ignore to the child directory - by default, or with a flag or config option. I believe this honors the spirit of what svn:ignore is supposed to accomplish. Pro: It is what a lot of people would expect. Con: It is what a lot of people wouldn't expect. I think a lot of users would welcome this functionality, though. They do complain that svn:ignore isn't inherited. I hate to suggest yet another config option, as relying on config options to settle design conflicts is a sure path to madness, but it may actually be reasonable here, given the potential utility. (Come to think of it, I bet a way to specify "all new directories" in auto-props would be welcome too.) -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
