Re: Last-Modified HTTP header in GET responses

2019-09-02 Thread Branko Čibej
On 02.09.2019 16:20, Johan Corveleyn wrote: > On Fri, Jan 15, 2016 at 1:58 PM Ivan Zhakov wrote: >> On 7 January 2016 at 10:34, Ivan Zhakov wrote: >>> On 6 January 2016 at 08:14, Greg Stein wrote: Personally, I'd be more interested in the effects on the network and its caching ability.

Re: [PATCH] test-deps += svnmover

2019-09-02 Thread Daniel Shahaf
Julian Foad wrote on Mon, 02 Sep 2019 14:23 +00:00: > Daniel Shahaf wrote: > > In current master, «./autogen.sh && ./configure && make davautocheck» fails > > all svnmover tests. > > By default, 'make davautocheck' expects to find > 'tools/server-side/mod_dontdothat' has already been built; my f

Re: Python3 work [was: The run up to Subversion 1.13.0]

2019-09-02 Thread Nathan Hartman
On Mon, Sep 2, 2019 at 8:23 AM Julian Foad wrote: > Thanks. I see no reason to make a special effort to have swig-py > bindings still support Python 2 for Subversion 1.13 and 1.14-LTS. In > fact, it's probably best if we explicitly remove Py2 support for 1.14, > to avoid getting trapped in mainte

Re: [PATCH] test-deps += svnmover

2019-09-02 Thread Julian Foad
Daniel Shahaf wrote: In current master, «./autogen.sh && ./configure && make davautocheck» fails all svnmover tests. By default, 'make davautocheck' expects to find 'tools/server-side/mod_dontdothat' has already been built; my first reaction then was to run 'make tools' which builds that and

Re: Last-Modified HTTP header in GET responses

2019-09-02 Thread Johan Corveleyn
On Fri, Jan 15, 2016 at 1:58 PM Ivan Zhakov wrote: > On 7 January 2016 at 10:34, Ivan Zhakov wrote: > > On 6 January 2016 at 08:14, Greg Stein wrote: > >> Personally, I'd be more interested in the effects on the network and its > >> caching ability. Do we really need to save CPU/IO on the server

Re: Python3 work [was: The run up to Subversion 1.13.0]

2019-09-02 Thread Julian Foad
Branko Čibej wrote: What Py3 support are we talking about anyway? svn build? svn test suite? swig-py bindings? This is about the work that's happening on the swig-py3 branch. So: that would be support for building the swig-py bindings for both Python3 and Python2. Trunk only support Python2 whi

Re: Python3 work [was: The run up to Subversion 1.13.0]

2019-09-02 Thread Branko Čibej
On 02.09.2019 11:45, Julian Foad wrote: >> Troy Curtis Jr wrote: >>> James McCoy wrote: Finishing(?) and merging the Python3 support would be ideal.  That would give one release for broader feedback before being in an LTS release. >>> >>> It needs to get reintegrated with trunk again

Python3 work [was: The run up to Subversion 1.13.0]

2019-09-02 Thread Julian Foad
Troy Curtis Jr wrote: James McCoy wrote: Finishing(?) and merging the Python3 support would be ideal. That would give one release for broader feedback before being in an LTS release. It needs to get reintegrated with trunk again with the latest changes, but the linux side of the house was lo

Re: The run up to Subversion 1.13.0

2019-09-02 Thread Johan Corveleyn
On Mon, Sep 2, 2019 at 3:42 AM Troy Curtis Jr wrote: > > > > On Fri, Aug 30, 2019, 7:13 PM James McCoy wrote: >> >> On Fri, Aug 30, 2019 at 05:12:21PM +0100, Julian Foad wrote: >> > 2. As 1.13 is only weeks away, there is little point in making any further >> > 1.12.x patch releases from now on,

Re: The run up to Subversion 1.13.0

2019-09-02 Thread Stefan Sperling
On Sun, Sep 01, 2019 at 09:41:47PM -0400, Troy Curtis Jr wrote: > It needs to get reintegrated with trunk again with the latest changes, but > the linux side of the house was looking good. It was in trying to get my > Windows Dev environment back up and running again that got me frustrated > and ga