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

Re: svn commit: r1546619 - /subversion/branches/fsfs-ucsnorm/BRANCH-README

From: Thomas ┼kesson <thomas_at_akesson.cc>
Date: Sun, 8 Dec 2013 12:26:46 +0100

On 8 dec 2013, at 10:56, Branko ─îibej <brane_at_wandisco.com> wrote:

>> You might remember from back when I did some specification work (in the wiki) that I am a strong proponent of the "normalization-preserving" approach to the problem. I believe n-p makes many issues dealing with existing repositories much easier to manage, in most cases go away completely unless there are actually normalization conflicts.
>
> Agreed. The only "problem" with this approach is that it affects performance; but I'm hoping that the effect will be minor.

Yes, a strong reason to implement in FS-layer; keeping the performance effect as low as possible.

>
>> E.g. the issue raised by Bert 2013-11-24 regarding mergeinfo is not a problem with n-p (I guess without thinking too much about it).
>
> Mergeinfo really has all the same problems as paths; in both cases, both the server and the client have to be normalization-agnostic and -preserving in all their path and mergeinfo operations.

Wouldn't n-p be sufficient? Which incidentally is the default/legacy behaviour.

Mergeinfo should reference paths with the exact path of the file/folder, I suppose. Do you expect to find legacy data where mergeinfo contains paths that are not byte-equal to the repository paths?

/Thomas ├ů.
Received on 2013-12-08 12:27:25 CET

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