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

Re: Compromize proposal [Was: Forcing svn:eol-style=native on files with "binary" mime types?]

From: Andreas Keil <rien_at_nurfuerspam.de>
Date: 2005-09-29 12:00:33 CEST

"Aleksey Nogin" <aleksey@nogin.org> wrote:
> OK, I think I have an idea for a compromise that people might be more
> likely to find acceptable. Here is my proposal:
> 1) Compile a list of "known binary" mime types (with
> application/octet-stream being the first in the list, obviously),
> replacing the current clearly imperfect "text/binary" classification with
> a more accurate.
> 2) Leave the current behavior of "svn ps svn:eol-type" for the "known
> binary" mime types, but remove it from the "unknown" ones ("unknown" =
> those that are neither on the "known text" list nor on "known binary"
> one). Basically, if subversion does not know a mime type, it should just
> trust that the users know better.
> 3) Change the auto-props behavior so that it's always possible to combine
> eol-type with even a "known binary" mime type via auto-props.
> 4) (Optional) Add the application/xhtml+xml and application/xml types to
> the "known text" list.
> 5) (Long-term) Allow users to override/augment the built-in lists of known
> text/known binary mime types via local config files.
> What do people think? If we can agree on this being a reasonable plan, I
> would be willing to try implementing 1-4 (although I have no experience
> with subversion code, so I can not guarantee quick success).

All of your proposal seems reasonable to me and I would be thankful if you
implemented it.

Thanks a lot,

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 29 12:23:54 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.