> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> Sent: 21 May 2002 19:50
> We have some properties in the "svn:" namespace that are only
> meaningful for files, and some that are only meaningful for dirs:
>
> svn:mime-type ==> files
> svn:ignore ==> directories
> svn:eol-style ==> files
> svn:keywords ==> files
> svn:executable ==> files (*)
> svn:charset ==> files
> svn:externals ==> directories
>
> (* Yes, Unix overloads "executable" to have a meaning for directories,
> but that's not what we document the executable property to mean, so I
> don't think Subversion should support that overloading.)
>
> Since Subversion manages the "svn:" property namespace anyway, maybe
> we should protect against setting such properties on the wrong kind of
> target? Of course, user can pass --force to override:
>
> $ svn propset svn:mime-type "text/plain" .
> Error: "svn:mime-type" is for files, blah blah, use --force to override
> $ svn propset --force svn:mime-type "text/plain" .
> property `svn:mime-type set on '.'
> $
>
> Thoughts? Objections?
This has probably been shot down before, but what about letting files
inherit props set on the directory. This would go for svn:charset,
svn:eol-style and possibly svn:keywords.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 21 20:22:13 2002