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

Re: svn:mime-type and detecting mergeability

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-08-22 19:12:48 CEST

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> Eric Gillespie <epg@pretzelnet.org> writes:
> > He thinks this should be a repository option (which places it
> > post-1.0, waiting on the mechanism for the repository to send the
> > client configuration info), but i'm not so sure. After all,
> > merging is a client-side operation. Nevertheless, the web
> > editors should not have to jump through hoops to get configured.
> > Maybe the best way would be to have both repo and client options,
> > with the latter overriding the former.
> That sounds good to me. And we can implement the client side now,
> leaving the repository side for post-1.0.
> Anyone see a problem? If not, Eric, can you file the feature request?

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.

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:15:49 2002

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.