[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-25 11:56:49 CEST

"Branko Cibej" <brane@xbc.nu> wrote in message
news:43366DF3.7010004@xbc.nu...
[...]
>>>The only time you actually _need_ svn:mime-type is when you're serving
>>>pages on a HTTP server directly from the repository.
>>Right, but then I don't like SVN to force wrong assumptions about a file's
>>property.
> I don't see how it does.

By suppressing the svn:eol-style propery for all application/* files.

>> So what do you think about my porposal of using MIME type lists for
>> assumptions about mergeability/diffabiliry but letting the user override
>> those guesses?
> You can override those guesses today; application/octet-stream will always
> be binary; no svn:mime-type will always mean text. If we assume that a
> more complete MIME type list will happen, then we're talking about edge
> cases here.

The problem today is that setting the correct MIME type for xml (and other)
files prevents a correct handling of EOL markers. This may be solved by
creating a more complete MIME list like you proposed. I just wasn't sure if
the SVN developers really want to update that list all the time. Anyways,
your proposal of doing it like that would be fine as long as SVN doesn't
exhibit some default behaviour for unknown MIME types.

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 25 11:59:48 2005

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