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

Re: Using APACHE_2_0_BRANCH not HEAD was Re: recent apr change?

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-01-06 21:01:01 CET

On Mon, Jan 06, 2003 at 01:28:04PM -0600, Ben Collins-Sussman wrote:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
> > Justin Erenkrantz wrote:
> >
> > >
> > > Feel free to also revert the commit to mod_dav_svn that calls
> > > ap_lookup_provider just for that tag if you like. Or, however you'd
> > > do that in subversion. I'm not really sure. =) It'd be a good
> > > exercise, methinks. (Actually, how would you do this?) -- justin
>
> I don't understand; is ap_lookup_provider *only* in httpd 2.1?

No. It is also on APACHE_2_0_BRANCH, which is the "soon to be" 2.0.44. We
can snap either httpd 2.1-dev or the branch; we should be able to work with
either as long as it is the head or the branch tip.

> Seeing as how we're going to start changing mod_dav's pool usage, and
> possibly it's API (#issue 773),

We aren't sure whether and how the pool usage will change in mod_dav. But if
we do, then it would be for 2.0 as well as 2.1. And I'm not yet convinced
the API would change. Even if it does, then we might manage that for both
versions.

So... don't be so quick to jump to 2.1 just yet.

>...
> > i think you'd want to branch it, then check out a copy and 'svn merge
> > -r
> > FOO:BAR http://svn.collab.net/repos/svn/trunk' where FOO:BAR is the
> > commit that introduced the part you wanted to revert.
>
> Why branch it at all? Just run 'svn merge -r4255:4254 .; svn commit'.

Leave it in, but get a newer Apache.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 6 21:00:13 2003

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.