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

Re: Provider encountered an error while streaming a REPORT response

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Mon, 12 Sep 2011 22:24:35 -0400

On Mon, Sep 12, 2011 at 6:15 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:

> We bumped the SQLite requirement to the rather recent 3.6.18 because of
> bugs/features we needed.
>
> On the other hand, the minimum Python is 2.4 and the minimum APR is 0.9.
> They are old enough to go to grade school.

Well, yes. And you nor the Subversion team should have to to code to
such old standards simply to support out of date operating systems.
The problem is that when someone pops up and says "I must have this
current version on RHEL 4 because its use is mandated", or as happened
to me a ways back "on SCO OpenServer 5", "Debian Etch", or other out
of date operating systems, The idea that you can "just compile from
the source tarball" is not borne out by my experience nor, in the case
of RHEL 4, by actually testing it.

Interestingly, I've just run some casual tests with the "serf" library
and subversion-1.6.17, which gets us away from the neon
incompatibilities. It's promisijng: do people really see that much
performance benefit in the clients with serf instad of neon? And have
people tested with the 1.0.0 release of serf?
Received on 2011-09-13 04:25:09 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.