On 22.08.2014 12:56, Stefan Sperling wrote:
> On Fri, Aug 22, 2014 at 01:31:08PM +0200, Stefan Fuhrmann wrote:
>> People will get an error if one of the currently released 1.8 server
>> with revprop caching enabled or svnadmin change a revprop. In
>> that case, a 1.9 process using revprop caching w
On Fri, Aug 22, 2014 at 1:56 PM, Stefan Sperling wrote:
> On Fri, Aug 22, 2014 at 01:31:08PM +0200, Stefan Fuhrmann wrote:
> > People will get an error if one of the currently released 1.8 server
> > with revprop caching enabled or svnadmin change a revprop. In
> > that case, a 1.9 process using
On Fri, Aug 22, 2014 at 01:31:08PM +0200, Stefan Fuhrmann wrote:
> People will get an error if one of the currently released 1.8 server
> with revprop caching enabled or svnadmin change a revprop. In
> that case, a 1.9 process using revprop caching will error out upon
> revprop access.
>
> Local m
On Fri, Aug 22, 2014 at 12:57 PM, Stefan Sperling wrote:
> On Fri, Aug 22, 2014 at 12:50:40PM +0200, Stefan Fuhrmann wrote:
> > Remaining restrictions:
> >
> > * All processes modifying revprops must use 1.9 or later libraries
> > or revprop caching cannot be used.
>
> Does this mean that using
On Fri, Aug 22, 2014 at 12:50:40PM +0200, Stefan Fuhrmann wrote:
> Remaining restrictions:
>
> * All processes modifying revprops must use 1.9 or later libraries
> or revprop caching cannot be used.
Does this mean that using file:// with 'svn' < 1.9, or using svnadmin
or svnlook < 1.9, won't be
Situation.
In 1.8, revprop caching only works if *all* processes accessing the
same repository
1. Are located on the same machine.
2. Have revprop caching enabled.
The problem with this is that in 1.8
* we did not mention the restriction in the release notes,
* have no way to detect a violation
6 matches
Mail list logo
