You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Aaron Bannert <aa...@clove.org> on 2002/11/23 20:31:28 UTC
Re: cvs commit: httpd-site/docs/dev anoncvs.txt devnotes.html how-to-release.html
Didn't we rename this repository from httpd-2.0 to httpd? I see a
symlink
on icarus from httpd-2.0 --> httpd so both work the same, so we might
want to start encouraging use of the new "real" repo name.
-aaron
On Saturday, November 23, 2002, at 11:28 AM, wrowe@apache.org wrote:
> wrowe 2002/11/23 11:28:42
>
> Modified: docs/dev anoncvs.txt devnotes.html how-to-release.html
> Log:
> Reflect the commands for the APACHE_2_0_BRANCH split.
>
> Revision Changes Path
> 1.2 +6 -2 httpd-site/docs/dev/anoncvs.txt
>
> Index: anoncvs.txt
> ===================================================================
> RCS file: /home/cvs/httpd-site/docs/dev/anoncvs.txt,v
> retrieving revision 1.1
> retrieving revision 1.2
> diff -u -r1.1 -r1.2
> --- anoncvs.txt 21 Nov 2001 07:31:47 -0000 1.1
> +++ anoncvs.txt 23 Nov 2002 19:28:42 -0000 1.2
> @@ -60,9 +60,9 @@
> The password is "anoncvs" (without the quotation marks) for
> both servers.
>
> -To check out the current development tree:
> +To check out the stable Apache 2.0 release tree:
>
> - user@host:~$ cvs checkout httpd-2.0
> + user@host:~$ cvs checkout -r APACHE_2_0_BRANCH httpd-2.0
> cvs server: Updating httpd-2.0
> U httpd-2.0/ABOUT_APACHE
> U httpd-2.0/Announcement
> @@ -98,6 +98,10 @@
> U apr-util/test/.cvsignore
> U apr-util/test/Makefile.in
> U apr-util/test/testdbm.c
> +
> +
> +To check out the current Apache 2.1 development tree, use the same
> +commands as above, omiting the -r APACHE_2_0_BRANCH flag.
>
...
Re: cvs commit: httpd-site/docs/dev anoncvs.txt devnotes.html
how-to-release.html
Posted by "William A. Rowe, Jr." <wr...@apache.org>.
At 01:31 PM 11/23/2002, Aaron Bannert wrote:
>Didn't we rename this repository from httpd-2.0 to httpd? I see a symlink
>on icarus from httpd-2.0 --> httpd so both work the same, so we might
>want to start encouraging use of the new "real" repo name.
Agreed... I'll go back over it all.