Forcing svn:eol-style=native on files with "binary" mime types?
From: Aleksey Nogin <aleksey_at_nogin.org>
Date: 2005-09-22 02:35:00 CEST
I have a number of files that should use native eols, but should not be
svn: File 'foo' has binary mime type property
Even --force does not help convince subversion that I know what I am
And there seems to be no make this work in auto-props - if I use
*.foo = svn:eol-style=native;svn:mime-type=application/x-foo
then "svn add xyz.foo"
- "silently" adds the file with the correct svn:mime-type set, but no
If I reorder the two properties in the auto-props line, nothing changes.
Is there a way to set svn:eol-style w/o removing the svn:mime-type and
a) Trying to force it with "svn ps --force svn:eol-style" does not work
b) There is no way to combine svn:eol-style with
c) If I do it in different order, then it does allow it (I am actually
d) That "svn add" leaves things in half-finished state (w/o even
Are there any issues filed on this? Thanks!
P.S. I tried raising this question in users@ , but have not gotten any
-- Aleksey Nogin Home Page: http://nogin.org/ E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal) Office: Moore 04, tel: (626) 395-2200 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Thu Sep 22 02:35:44 2005 |
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.