Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of lesmikesell@gmail.com
 designates 209.85.216.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1319647175.22361.140660990771101@webmail.messagingengine.com>
References: <727D8E16AE957149B447FE368139F2B508A6FFEE@SERVER10>
	<041501cc93ee$d2d27850$787768f0$@qqmail.nl>
	<1319647175.22361.140660990771101@webmail.messagingengine.com>
Date: Wed, 26 Oct 2011 11:54:24 -0500
Message-ID: 
 <CAOAgVpzq3GittEdVPjQt+x8R63REGDssG_DWUxEC1Zk7b+cVNQ@mail.gmail.com>
Subject: Re: Property encoding (was: Error during svnadmin load (svnadmin:
 E125005: Cannot accept non-LF line endings in 'svn:log' property))
From: Les Mikesell <lesmikesell@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Bert Huijben <bert@qqmail.nl>, Markus Schaber <m.schaber@3s-software.com>,
	users@subversion.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Oct 26, 2011 at 11:39 AM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
>> > Could svnsync mistakenly "fix" a binary property which happens to contain
>> > CR-LF byte sequences?
>>
>> Within the svn:* namespace there are no binary properties.
>>
>
> But if svn 1.8 defines a binary svn:* prop, then svnsync 1.7 will try and normalize its line endings :-(

That's one of those 'if it hurts, don't do it...' things.   While you
always need to know if something is text or not to handle local text
conventions in a usable way, it would seem awkward for svn to assume
that revision contents are binary unless told otherwise, but have the
opposite convention for svn:* properties.   Better to just never allow
non-text there.

-- 
  Les Mikesell
    lesmikesell@gmail.com