Re: move certain svn props to top level path?

Branko Čibej wrote on 2018-04-15:
> On 15.04.2018 21:01, Stefan wrote:
> > On 05/04/2018 00:09, Stefan wrote:
> >> I'm not sure if there are other tools around using these. I'm talking
> >> here TSVN which utilizes all of these properties and yes, it's treating
> >> them as inheritable ones. There seem to be other tools using these as
> >> well [1/2], though I can't say for sure whether they are treating them
> >> as inheritable (though I'd strongly suspect so).
> >> https://markphip.blogspot.de/2007/01/integrating-subversion-with-your-issue.html

Mark's blog post there says the spec was developed jointly with Subclipse so that's at least one other.

Did you (Stefan) check inheritance works as expected?

The spec at

  http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt

(give the username 'guest' and no password to access it) says:

- If the properties are not set for a folder, the client should search upwards
  in the working copy for them until the working copy root is reached.

It doesn't say the client will search up into a parent folder in the repository that isn't in the WC.

That suggests your change may break quite a lot of use cases unless the info I found above is out of date.

If I have misunderstood something, then the Subversion feature "Inheritable properties" may possibly have made this "Just work", possibly; but I don't think so; but at least that feature should make it much easier to implement inheritance that searches up beyond the WC root to a folder that's only in the repository, if/when the various clients choose to do so.

> Tags should not change.
> +1 for removing those properties from branches.

That part I agree with.

- Julian
Received on 2018-04-15 22:56:37 CEST