You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Jens Seidel <je...@users.sourceforge.net> on 2006/03/23 09:42:35 UTC
Status of "property co-existence problems."?
Hi,
I noticed that setting properties is not commutable.
$ svn proplist --verbose tools8.xpm
$ svn propset svn:mime-type image/x-xpm tools8.xpm
property 'svn:mime-type' set on 'tools8.xpm'
$ svn propset svn:eol-style native tools8.xpm
svn: File 'tools8.xpm' has binary mime type property
$ svn propdel svn:mime-type tools8.xpm
property 'svn:mime-type' deleted from 'tools8.xpm'.
$ svn propset svn:eol-style native tools8.xpm
property 'svn:eol-style' set on 'tools8.xpm'
$ svn propset svn:mime-type image/x-xpm tools8.xpm
property 'svn:mime-type' set on 'tools8.xpm'
$ svn proplist --verbose tools8.xpm
Properties on 'tools8.xpm':
svn:mime-type : image/x-xpm
svn:eol-style : native
I googled for it and found http://svn.haxx.se/dev/archive-2004-10/1409.shtml
from Ben Collins-Sussman with subject "property co-existence problems." which
covers this. Also http://svn.haxx.se/users/archive-2003-10/0636.shtml.
Now I see in the FAQ that "image/x-xpixmap" is considered to be text file
but image/x-xpm isn't :-) (KDE considers image/x-xpm to be a proper mime type.)
I would like to know more about this. Maybe it's a good idea to fill a bug
so that it's possible to follow the discussion?
When will this nasty behaviour be fixed?
PS: I vote for evaluating svn:eol-style even if svn:mime-type is set.
Please CC: me.
Jens
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org