Re: move certain svn props to top level path?

2018-04-22 Thread Stefan
On 16/04/2018 09:15, Julian Foad wrote: > Tags should not change. > +1 for removing those properties from branches. That part I agree with. >>> >>> I'm not going to make a case out of this, but please be aware the >>> implications of keeping the incorrect/outdated props on the tags: >

Re: move certain svn props to top level path?

2018-04-16 Thread Stefan
On 16/04/2018 09:15, Julian Foad wrote: > Branko Čibej wrote: >> On 15.04.2018 23:42, Stefan wrote: >>> On 15/04/2018 22:56, Julian Foad wrote: [...] > - If the properties are not set for a folder, the client should search upwards    in the working copy for them until the working

Re: move certain svn props to top level path?

2018-04-16 Thread Julian Foad
Branko Čibej wrote: On 15.04.2018 23:42, Stefan wrote: On 15/04/2018 22:56, Julian Foad wrote: 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? I know for sure that it's working for

Re: move certain svn props to top level path?

2018-04-15 Thread Branko Čibej
On 15.04.2018 23:42, Stefan wrote: > On 15/04/2018 22:56, Julian Foad wrote: >> 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

Re: move certain svn props to top level path?

2018-04-15 Thread Julian Foad
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

Re: move certain svn props to top level path?

2018-04-15 Thread Branko Čibej
On 15.04.2018 21:01, Stefan wrote: > On 05/04/2018 00:09, Stefan wrote: >> On 04/04/2018 23:47, Branko Čibej wrote: >>> On 04.04.2018 23:12, Stefan wrote: Hi, atm we specify the following svn properties on trunk: * bugtraq:url * bugtraq:logregexp *

Re: move certain svn props to top level path?

2018-04-15 Thread Stefan
On 05/04/2018 00:09, Stefan wrote: > On 04/04/2018 23:47, Branko Čibej wrote: >> On 04.04.2018 23:12, Stefan wrote: >>> Hi, >>> >>> atm we specify the following svn properties on trunk: >>> >>> * bugtraq:url >>> * bugtraq:logregexp >>> * tsvn:logwidthmarker >>> * tsvn:projectlanguage >>>

Re: move certain svn props to top level path?

2018-04-04 Thread Stefan
On 04/04/2018 23:47, Branko Čibej wrote: > On 04.04.2018 23:12, Stefan wrote: >> Hi, >> >> atm we specify the following svn properties on trunk: >> >> * bugtraq:url >> * bugtraq:logregexp >> * tsvn:logwidthmarker >> * tsvn:projectlanguage >> * webviewer:revision >> * (possibly by the

Re: move certain svn props to top level path?

2018-04-04 Thread Branko Čibej
On 04.04.2018 23:12, Stefan wrote: > > Hi, > > atm we specify the following svn properties on trunk: > > * bugtraq:url > * bugtraq:logregexp > * tsvn:logwidthmarker > * tsvn:projectlanguage > * webviewer:revision > * (possibly by the time you read this, I added webviewer:pathrevision)

move certain svn props to top level path?

2018-04-04 Thread Stefan
Hi, atm we specify the following svn properties on trunk: * bugtraq:url * bugtraq:logregexp * tsvn:logwidthmarker * tsvn:projectlanguage * webviewer:revision * (possibly by the time you read this, I added webviewer:pathrevision) Since these properties are currently not set project