Ben Collins-Sussman <sussman@collab.net> writes:
> libsvn_wc is the *only* thing that pays attention to the concept of
> text-ness and binari-ness. So I don't understand why the solution
> should have anything to do with repository bits.
>
> A file has some svn:mime-type property; well and good, that value
> gets sent out to web browers in a Content-type: header. Maybe that
> value is xml/foo or whatever.
>
> Now libsvn_wc sees the property, and assumes that any non-NULL value
> that doesn't start with text/* means binariness -- no more contextual
> merging, when this file is really still a text file.
>
> So why not fix this purely on the client side? In a site-wide or
> personal ~/.subversion config area, set a list of mime-type patterns
> that are assumed to be text.
I think the idea is that the repository might be able to keep a
central database (as a text file, whatever) mapping mime-types to a
boolean indicating binary or text. Thus, clients wouldn't have to
contain all this knowledge themselves, they could get it from the
repos.
Not sure if this is good or bad, just trying to clarify Eric's
proposal.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 22 19:17:50 2002