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

Re: property co-existence problems.

From: Ben Reser <ben_at_reser.org>
Date: 2004-10-25 23:38:14 CEST

On Mon, Oct 25, 2004 at 03:33:11PM -0500, Ben Collins-Sussman wrote:
> 1. make eol-style always work, no matter what. removes the safeguard,
> possibly risks data corruption among newbies.


> 2. continue to expand svn's internal list of "texty" mime-types.
> The problem with #2 is that it just doesn't scale well. cmpilato
> predicts this problem is only going to get worse over time, and we
> won't be able to keep up. The fact that we've conflated
> "svn:mime-type" with "is textual and safe for contextual diffing" is
> arguably a mistake, despite the convenience.

-1 (Already vetoed changes like this in the past)
> An idea floating around the Chicago office is to add a new property:
> 'svn:text'. If this property exists, then it *authoritatively* means
> the property is text-y and safe for contextual diffing/merging. If it
> doesn't exist, then svn resorts to looking at 'svn:mime-type' to hazard
> a guess.
> Is this a reasonable solution? If people like it, I can file a new
> feature request.

-0 on this change.

I'd much rather see us introduce a configuration option that sets what
mime-types are text. Even if it's only client side for the time being.

I tend not to like overlapping options. svn:text feels very much that

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 25 23:38:35 2004

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.