You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rodent of Unusual Size <co...@decus.org> on 1997/07/13 17:15:20 UTC

Too much going into 1.2 tree?

    Erm, can anyone explain why the NT stuff is getting put into the 1.2
    tree?

% cvs update apache-1.2
cvs server: Updating apache-1.2
cvs server: Updating apache-1.2/cgi-bin
    :
cvs server: Updating apache-1.2/src/modules/proxy
cvs server: Updating apache-1.2/src/nt
P apache-1.2/src/nt/modules.c
P apache-1.2/src/nt/readdir.c
P apache-1.2/src/nt/readdir.h
cvs server: Updating apache-1.2/src/regex
    :

    I thought 1.2 was completely quiescent now (until the next set of
    undiscovered security fixes).

    I'm starting to have serious concerns about the value of branches
    versus creating separate modules..

    #ken    :-(}

Re: Too much going into 1.2 tree?

Posted by Ben Laurie <be...@algroup.co.uk>.
Rodent of Unusual Size wrote:

>     Erm, can anyone explain why the NT stuff is getting put into the
> 1.2
>     tree?
>
> % cvs update apache-1.2
> cvs server: Updating apache-1.2
> cvs server: Updating apache-1.2/cgi-bin
>     :
> cvs server: Updating apache-1.2/src/modules/proxy
> cvs server: Updating apache-1.2/src/nt
> P apache-1.2/src/nt/modules.c
> P apache-1.2/src/nt/readdir.c
> P apache-1.2/src/nt/readdir.h
> cvs server: Updating apache-1.2/src/regex
>     :

Weird. Have any of the other NT bits gone in? Could it be because they
are completely new files?

>     I thought 1.2 was completely quiescent now (until the next set of
>     undiscovered security fixes).

That was certainly the plan.

>     I'm starting to have serious concerns about the value of branches
>     versus creating separate modules..

Hmmm...

Cheers,

Ben.

--
Ben Laurie [Normal service will be resumed as soon as possible]



Re: Too much going into 1.2 tree?

Posted by Dean Gaudet <dg...@arctic.org>.
They're not really in the 1.2 tree unless they have an APACHE_1_2_X tag.
For example try doing a:

cvs export -r APACHE_1_2_X -d apache_1_2_x apache

and you should get essentially 1.2.1 (I don't think we've committed
anything 'cept doc changes after 1.2.1).

You're seeing the artifact Marc talked about. 

Dean

On Sun, 13 Jul 1997, Rodent of Unusual Size wrote:

>     Erm, can anyone explain why the NT stuff is getting put into the 1.2
>     tree?
> 
> % cvs update apache-1.2
> cvs server: Updating apache-1.2
> cvs server: Updating apache-1.2/cgi-bin
>     :
> cvs server: Updating apache-1.2/src/modules/proxy
> cvs server: Updating apache-1.2/src/nt
> P apache-1.2/src/nt/modules.c
> P apache-1.2/src/nt/readdir.c
> P apache-1.2/src/nt/readdir.h
> cvs server: Updating apache-1.2/src/regex
>     :
> 
>     I thought 1.2 was completely quiescent now (until the next set of
>     undiscovered security fixes).
> 
>     I'm starting to have serious concerns about the value of branches
>     versus creating separate modules..
> 
>     #ken    :-(}
>