> 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?
I'm +0 on this in general, but in the case of bundled directories (eg
on Mac OS X), I may very well want to set the mime-type of a
directory:
$ svn propset svn:mime-type "application/interface-builder" Main.nib
So I'm -1 on the mime-type limitation as I have evil evil plans for it
in the near future.
-Fitz
---------------------------------------------------------------------
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:07:21 2002