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

Re: [PATCH] Have svn require Neon 0.19.3

From: Bruce Atherton <bruce_at_callenish.com>
Date: 2002-02-26 22:27:38 CET

At 06:36 PM 2/25/2002 -0800, Greg Stein wrote:
>The net result is that we stick to a specific Neon release. If we specify a
>bounded range, then we could tweak the upper bound as new releases come out,
>but that upper-bound tweak has to be done manually. For example, today, we
>could set the bounds at (0, 19, 2) and (0, 19, 3). Let's say 0.19.4 comes
>out; if it works, then we could change the upper bound; but we can't do that
>before the release.

Is there any possibility that there could be an option to force acceptance
of whatever version of Neon is around? Or at least to allow a version that
goes past the stated maximum?

The reason I ask is that for nightly builds, you really want at least the
possibility of checking out the latest Neon from CVS. The earlier we can
detect API incompatibilities, the cheaper it will be to fix them.

Obviously, this wouldn't be used by the casual user. But there are times I
know better than Subversion does about what versions I want to test with,
and I'd really like the possibility of getting final say.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:10 2006

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.