[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Forcing svn:eol-style=native on files with "binary" mime types?

From: Andreas Keil <rien_at_nurfuerspam.de>
Date: 2005-09-22 12:30:05 CEST

>>That's why I proposed to remove this connection and to introduce a new
>>value for the svn:eol-style property which would tell SVN to stick with
>>the original eol markers.
>>
> Heh. You do that by not setting the svn:eol-style property at all.

You're right. In the meantime, I learned this keeps the original eol
markers, so it's fine for me.

[...]

>>Please help me in removing SVN's bug of assuming application/* to contain
>>binary data,
>>
> To be very specific here, SVN does *not* assume that application/* is
> binary, only that text/* is not.

Well, but why does it remove the svn:eol-style property from application/*
files then?

>> as this is *really* a bug, no matter what one thinks about possible
>> solutions to the eol problem.
>>
> Patches welcome. If you come up with a portable way to differentiate
> between text and non-text MIME types, I'll be happy to review and commit
> the patch.

That's the problem, I don't want SVN to differentiate between MIME types for
the purpose of guessing whether a file contains binary or text data. This
doesn't make sense since
1.) MIME types don't seem to be very well defined and are created every day.
2.) there doesn't exist a MIME type for every file type you can think of.

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 22 12:33:48 2005

This is an archived mail posted to the Subversion Dev mailing list.