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

Re: [RFC] [PATCH] Allow any Neon version from specified branches

From: Greg Stein <gstein_at_gmail.com>
Date: Mon, 22 Sep 2008 17:33:10 -0500

A blacklist is not appropriate. We would miss 0.30-dev, etc.

Again. +1 iff references to 0.29 and 0.27.{0,1} are removed.

(and yes, if you push me on inequality, I'm fine with blasting unknown
versions of apr, serf, bdb, sqlite, etc)

On Sep 22, 2008, at 17:19, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:

> Arfrever Frehtes Taifersar Arahesis wrote on Tue, 23 Sep 2008 at
> 00:04 +0200:
>> 2008-09-22 23:56:35 Greg Stein napisaƂ(a):
>>> Lose all mention of 0.29, and I'm +1 with that.
>> When I tested Subversion 1.5.2, all tests passed with Neon 0.29.0-
>> dev.
>> http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=142411
> Doesn't -dev mean "trunk"? If so, it's pretty much by definition not
> appropriate to list it in NEON_ALLOWED_LIST, which (as I understand
> it)
> means "Versions we tested and we know to work", since it is a moving
> target.
> Nonetheless, to support Neon trunk, we can ask those who build with it
> (just Arfrever, right? :)) to pass --disable-neon-version-check, or
> we can
> switch to a blacklist regime (and have NEON_DISALLOWED_LIST="0.27.0 0.27.1
> etc").

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-23 00:33:18 CEST

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

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