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

Re: Binary file checkin problem

From: Branko Čibej <brane_at_xbc.nu>
Date: 2005-05-24 12:56:31 CEST

Blair Zajac wrote:

> Ben Collins-Sussman wrote:
>> It's already the case that if svn:mime-type is set to a binary type,
>> then 'svn propset' will refuse to set the svn:eol-style or
>> svn:keywords properties. But apparently there are other ways to get
>> them to co-exist... I suspect that the svn:mime-type is set *after*
>> the text-munging ones, then you can end up with all three properties
>> set at once. So if there's a bug here to report, it's perhaps that
>> we aren't doing enough to prevent foot-shooting. :-)
> I filed an issue
> http://subversion.tigris.org/issues/show_bug.cgi?id=2309
> There's a script there that will reproduce this problem with one
> commit setting svn:mime-type and a following commit setting svn:keywords.

This is *not* a bug. Subversion is working as designed.

It has always been the policy on Subversion to have safe defaults, but
not to restrict flexibility. Setting svn:keywords on "binary" files is a
valid use case, because "binary" and "fixed-length records" are not
synonyms. As far as Subversion is concerned, "binary" only means
non-mergeable, it doesn't mean you shouldn't expand keywords. That's one
of the reasons we have a separate svn:keywords property.

-- Brane

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 24 12:59:03 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.