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

Re: Interpretation of SVN MIME type property

From: Marcus Rueckert <darix_at_web.de>
Date: 2005-09-20 14:31:11 CEST

On 2005-09-20 11:01:47 +0200, Andreas Keil wrote:
> Does anyone follow up this problem of SVN interpreting application/* MIME
> type files as binary? As a quick fix, this behaviour should be removed
> immediately as it's simply wrong. New solutions for determining whether a
> file contains binary or text data could be postponed and seeked in a
> thorough discussion but this bug should be fixed as soon as possible.
> For the solution discussion: Why not use SVN's already existing heuristics
> for determining a file's content and stick with SVN's eol-style property
> (adding an "unchanged" or "original" value) for giving the user a chance to
> deviate from SVN's guess?

lets assume we follow your idea:
1. svn allows you to set svn:eol-style only on text files.
2. a user adds a pdf file. the current heuristic says text. yes that can
happen with pdf.
3. the user sets eol-style
4. the binary chunk at the end of the pdf gets corrupted.

the better idea is imho to allow the user to specify which mimetypes svn
can/should handle as text. there is already a hard coded list for that.
if you move that list into $HOME/.subversion/config you configure it at
runtime. enough? once we get pushing server side configs to the client
this process can be optimized for large teams.

just my 2 cents


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 20 14:33:26 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.