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

Re: svn commit: r1441814 - in /subversion/trunk/subversion: svn/ tests/cmdline/

From: Stefan Sperling <stsp_at_elego.de>
Date: Sun, 3 Feb 2013 12:36:55 +0100

On Sat, Feb 02, 2013 at 11:38:56PM +0100, Bert Huijben wrote:
>From my users I hear that another way this property is introduced is via conversions from other version management systems. Visual SourceSafe (long dead, but still used in a lot of small shops) marks UTF-8 files with a BOM as binary when it does an auto detect.
> (Well what would you guess for a system that wasn’t really updated since that format became popular)
>
> Most conversion tools just copy the binary flag, and there you have this problem on all your historic utf-8 files.
> (Where I worked we had this problem on all .xml files previously stored in sourcesafe).
>
>
> I don't see a lot of users accidentally adding invalid properties themselves.

I agree that automatic creation of such properties is also a problem.
However, it is not the problem that was discussed in the referenced
users@ thread. This really is about the rare case where a novice user
makes a mistake, nothing more.
Received on 2013-02-03 12:37:44 CET

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.