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

Re: svn:auto-props: property specified in a parent dir but not specified in a subdir

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Tue, 18 Oct 2016 23:01:57 +0200

On Tue, Oct 18, 2016 at 1:35 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Branko Čibej wrote on Tue, Oct 18, 2016 at 13:08:37 +0200:
>> It is. I don't think there's any way we can /not/ make it backwards
>> incompatible, given the current implementation. Which is why I think we
>> should just admit that current behaviour is a bug.
>> Either that, or introduce a new property that behaves sensibly.
> Some IRC discussion lead us to svn_prop_name_is_valid(), which requires
> that the first character of a property name be alphabetic or colon or
> underscore.
> Brane therefore proposes «*.txt == propname=propval» for the "override"
> syntax, and keep «*.txt = propname=propval» for the "overlay" syntax.
> This change would be backwards compatible: this syntax does not have
> a meaning currently. 1.9 clients just ignore it.
> We can bikeshed about finding a syntax that looks less like
> a C comparison, of course. We can't use =: because property names can
> start with a colon, we can't use := because filename patterns can end
> with a colon, but any other option is open.

Great idea. And I like that color of bikeshed :-).

Another option would be to introduce a "subtract" syntax, with =- or
=!, but I don't know if that would be easier / better for the user (in
that case, he'd have to specify the *.txt pattern two times, to
subtract svn:eol-style with =!, and add svn:mime-type with =).

Received on 2016-10-18 23:02:28 CEST

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