cvs commit: apache-site related_projects.html
ben 98/09/28 07:33:51 Modified:.related_projects.html Log: Duh! Some people couldn't find the link! Revision ChangesPath 1.32 +3 -1 apache-site/related_projects.html Index: related_projects.html === RCS file: /export/home/cvs/apache-site/related_projects.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- related_projects.html 1998/08/17 06:58:46 1.31 +++ related_projects.html 1998/09/28 14:33:50 1.32 @@ -61,7 +61,9 @@ States you can use it for non-commercial and commercial purposes for free.P -Inside the United States in order to use Apache with SSL commercially you may want to look at A HREF=#strongholdStronghold/A or A HREF=#ravenRaven/A. +Inside the United States in order to use Apache with SSL commercially you may want to look at A HREF=#strongholdStronghold/A or A HREF=#ravenRaven/A.P + +A HREF=http://www.apache-ssl.org/;Get Apache-SSL from here/A. PHR
cvs commit: apache-devsite bugdb-policies.html
coar98/09/28 07:49:47
Modified:.bugdb-policies.html
Log:
Add descriptions of the various editing fields and how to use them.
Revision ChangesPath
1.3 +186 -6apache-devsite/bugdb-policies.html
Index: bugdb-policies.html
===
RCS file: /export/home/cvs/apache-devsite/bugdb-policies.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- bugdb-policies.html 1998/08/07 09:16:49 1.2
+++ bugdb-policies.html 1998/09/28 14:49:46 1.3
@@ -7,7 +7,7 @@
STYLE TYPE=text/css
!--
TD { font-size: smaller }
- --
+ // --
/STYLE
/HEAD
!-- Background white, links blue (unvisited), navy (visited), red (active)
--
@@ -30,6 +30,8 @@
/LI
LIA HREF=#guidelinesGeneral Guidelines/A
/LI
+ LIA HREF=#fieldsPR Fields/A
+ /LI
LIA HREF=#statesPR States/A
MENU
LIA HREF=#openopen/A
@@ -103,6 +105,184 @@
/LI
/UL
HR
+ H2A NAME=fieldsPR Fields/A/H2
+ P
+ The PR editing form has a number of different fields on it. Some are
+ pull-down lists, some are free-form text boxes, and some are buttons or
+ checkboxes. Here's a description of what they are and how to use
+ them.
+ /P
+ P
+ STRONGWhen filling in free-form text boxes, use the Enter or Return
+ key to insert hard newlines in order to keep the line-length short!
+ Try to keep the horizintal scrollbar inactive./STRONG
+ /P
+ DL COMPACT
+ DTSAMPDO NOT send mail about this change/SAMP
+ /DT
+ DD
+P
+Just as you might expect, this controls whether the update to the
+bugdb will also result in a mail message. This should ordinarily be
+left 'off'; only check this box if you are making cosmetic changes
+that don't need attention (such as changing the 'release' field).
+/P
+ /DD
+ DTSAMPEditor (you)/SAMP
+ /DT
+ DD
+P
+This field should initially contain your username or email address.
+Don't change it. If it's blank, put in your username (if you have
+an account on Taz) or your email address. Whatever value you
+enter must match your access name to the bugdb.
+/P
+ /DD
+ DTSAMPNew synopsis/SAMP
+ /DT
+ DD
+P
+The synopsis is a one-line abstract of the PR. STRONGOnly change
+this field if the original synopsis is incorrect or unclear./STRONG
+/P
+ /DD
+ DTSAMPOriginator/SAMP
+ /DT
+ DD
+P
+This field contains the email address of the PR's submitter. This
+ordinarily doesn't need to be changed unless you're correcting
+an invalid SAMPpending/SAMP-category entry.
+/P
+ /DD
+ DTSAMPClass/SAMP
+ /DT
+ DD
+P
+This pull-down list identifies the class of problem being described by
+the PR. The canonical value is SAMPsw-bug/SAMP; the next most
+common is SAMPchange-request/SAMP. When editing a PR, verify that
+the value actually applies to the report, and change it if necessary.
+/P
+ /DD
+ DTSAMPRelease/SAMP
+ /DT
+ DD
+P
+In almost all cases, this should simply contain the Apache release
+version, without any embellishments. 1.3.2, 1.1.3, 1.3b6-dev
+are all acceptable. The only time more text is really appropriate
+in this field is if the PR refers to one of the non-Apache projects,
+such as SAMPmod_jserv/SAMP. When editing a PR, try to shorten
+this field if possible, since it widens the PR summary display
+unnecessarily.
+/P
+ /DD
+ DTSAMPSeverity/SAMP
+ /DT
+ DD
+P
+Possible values for this are critical, serious, and non-critical.
+Make a judgment call about whether the current setting is truly
+appropriate before changing the value. A PR that has been in feedback
+state for several weeks, for instance, is definitely a candidate
+for downgrade from critical. If it were EMtruly/EM critical,
+the submitter would have responded.
+/P
+ /DD
+ DTSAMPNew state/SAMP
+ /DT
+ DD
+P
+If you are modifying the state of a PR, this is where you do it.
+See the A HREF=#statesnext section/A for information about
+possible values and state transitions. Note that if you change the
+state of a PR, you STRONGmust/STRONG add an explanation in the
+next field.
+/P
+ /DD
+ DTSAMPIf state changed, give the reason here. To add a comment
+to the case, enter text here without changing the state/SAMP
+ /DT
+ DD
+P
+Any time the state of a PR is changed, the alteration must be accompanied
+by an explanation. This is a free-form text box, so you can word things
+however you like. It's recommended that you start with a blank line
cvs commit: apache-1.3 README.configure
coar98/09/28 08:46:40 Modified:.README.configure Log: Correct some hyphen/underbar confusions. PR: 3075 Submitted by: Ryan Bloom [EMAIL PROTECTED] Reviewed by: Ken Coar Revision ChangesPath 1.14 +8 -8 apache-1.3/README.configure Index: README.configure === RCS file: /export/home/cvs/apache-1.3/README.configure,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- README.configure 1998/06/28 15:42:21 1.13 +++ README.configure 1998/09/28 15:46:39 1.14 @@ -13,7 +13,7 @@ The basic goal is to provide the following commonly known and expected procedure for out-of-the-box building and installing a package like Apache: -$ gunzip apache-1.3.X.tar.gz | tar xvf - +$ gunzip apache_1.3.X.tar.gz | tar xvf - $ ./configure --prefix=PREFIX [...] $ make $ make install @@ -224,7 +224,7 @@ [optionally you now have the chance to prepare or add more third-party modules to the Apache source tree] -$ cd ../apache-1.3.X +$ cd ../apache_1.3.X $ ./configure --prefix=/path/to/apache \ --activate-module=src/modules/perl/libperl.a \ [--enable-shared=perl] @@ -242,17 +242,17 @@ $ gunzip apache_1.3.X.tar.gz | tar xvf - $ gunzip php-3.0.tar.gz | tar xvf - -$ cd apache-1.3.X +$ cd apache_1.3.X $ ./configure --prefix=/path/to/apache $ cd ../php-3.0 -$ ./configure --with-apache=../apache-1.3.X +$ ./configure --with-apache=../apache_1.3.X $ make $ make install [optionally you now have the chance to prepare or add more third-party modules to the Apache source tree] -$ cd ../apache-1.3.X +$ cd ../apache_1.3.X $ ./configure --prefix=/path/to/apache \ --activate-module=src/modules/php3/libphp3.a $ make @@ -262,17 +262,17 @@ $ gunzip apache_1.3.X.tar.gz | tar xvf - $ gunzip php-3.0.tar.gz | tar xvf - -$ cd apache-1.3.X +$ cd apache_1.3.X $ ./configure --prefix=/path/to/apache $ cd ../php-3.0 -$ ./configure --with-shared-apache=../apache-1.3.X +$ ./configure --with-shared-apache=../apache_1.3.X $ make $ make install [optionally you now have the chance to prepare or add more third-party modules to the Apache source tree] -$ cd ../apache-1.3.X +$ cd ../apache_1.3.X $ ./configure --prefix=/path/to/apache \ --activate-module=src/modules/php3/libphp3.a \ --enable-shared=php3
cvs commit: apache-2.0 STATUS
lars98/09/28 10:33:15 Modified:.STATUS Log: Revision ChangesPath 1.42 +28 -21apache-2.0/STATUS Index: STATUS === RCS file: /home/cvs/apache-2.0/STATUS,v retrieving revision 1.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- STATUS1998/09/25 19:44:59 1.41 +++ STATUS1998/09/28 17:33:14 1.42 @@ -25,17 +25,19 @@ segments should persist until the refcount drops to zero. It would be cool if pools could be created in such segments to allow things like shared tables and arrays. - +1: Roy, Paul, Ken, Ralf, Martin + +1: Roy, Paul, Ken, Ralf, Martin, Lars * Apache ports project - simple-to-install (a la CPAN) one-off tools, scripts (such as counters, guest books, et cetera) +1: Roy, Paul, Ken, Ralf, Martin David Southwell has volunteered to work on this. + -0: Lars [If we do this for modules only I'm +1, but + I'm not very happy with scripts, tools or other stuff.] * Embed API documentation in the source, a la Java docs, so a script can extract the parameters and description and build a dictionary. If we do this, it needs to be *mandatory* in the style guide. - +1: Ken + +1: Ken, Lars * Abstract the '+/-' capabilities of the Options keyword so other directives can use it without re-inventing the square peg. @@ -51,7 +53,7 @@ formats that bear a faint resemblance to other usages (such as allowing =~ and !~) in other languages, and provide for caseless matches. - +1: Roy, Ken, Martin + +1: Roy, Ken, Martin, Lars Martin sez: I've been thinking about replacing the parser by a recursive descent parser which would reduce complexity tremendously. @@ -62,7 +64,7 @@ to have things like the arrays, tables, pools, and related primitives moved into a library of which httpd is just a client and other things can be too. - +1: Roy, Paul, Jim, Ken, Ralf, Martin + +1: Roy, Paul, Jim, Ken, Ralf, Martin, Lars * Replace the current Unix compilation model (Configuration.tmpl, home-brew Configure script) with the autoconf toolset. @@ -73,11 +75,12 @@ varies from the above such that if it's shown that the autoconf toolset can do what we want, with less headache than what we have, then we go for it) - +1: Jim, Ken, Marc, MarkC, Ben, Paul, Martin + +1: Jim, Ken, Marc, MarkC, Ben, Paul, Martin, Lars * The autoconf toolset should include all three: autoconf, automake, and libtool. +1: Brian, Jim, Roy, Dean, Ken, Ralf, Martin + +0: Lars * Whatever we do regarding autoconf, we should be able to configure to build objects other than in the source tree. autoconf allows for this... you @@ -85,7 +88,7 @@ platforms... or even on a single platform, one copy with profiling another without. (There are a lot of possibilities: creating shadow trees, VPATH-style Makefile settings, etc.) - +1: Dean, Roy, Paul, Ralf, Martin + +1: Dean, Roy, Paul, Ralf, Martin, Lars * One of the main restrictions on Apache has been that we must assume a very low-level common denominator for the OSs out there. For example, @@ -116,7 +119,8 @@ if they can help parallelize development or simplify the core code.] * multithreading. -+1: Brian, Ken, Jim, Paul, Sameer, Marc, Ralf, MarkC, Ben, Martin, Roy ++1: Brian, Ken, Jim, Paul, Sameer, Marc, Ralf, MarkC, Ben, Martin, +Roy, Lars o Thread Abstraction +1: Sameer, Marc, MarkC, Ben, Dean, Paul, Martin, Roy, Ralf Status: nobody has volunteered yet @@ -124,12 +128,13 @@ * revamped process model (Dean's proposal) Dean says: it's hard to do the multithreading work cleanly without considering a bunch of this -+1: MarkC, Paul, Dean, Martin, Roy, Ralf ++1: MarkC, Paul, Dean, Martin, Roy, Ralf, Lars Marc (+1 on much of it; threads aren't enough for perf.), Status: nobody has volunteered yet * new layered I/O. -+1: Brian, Ken, Dean, Jim, Paul, Sameer, Marc, Ralf, MarkC, Ben, Roy ++1: Brian, Ken, Dean, Jim, Paul, Sameer, Marc, Ralf, MarkC, Ben, +Roy, Lars Status: Ken has volunteered. o sfio @@ -152,7 +157,7 @@ The only problem is reclaiming buffers so that a large SSI won't suck up all available memory just sending it out the pipe.] +1: Dean, Marc, Ben, Paul, Martin, Roy -+0: Jim [what about examples? Portability concerns?], Ralf ++0: Jim [what about
cvs commit: apache-1.3 INSTALL
coar98/09/28 12:28:02 Modified:.INSTALL Log: Correct typo in mod_autoindex's name. PR: 3092 Submitted by: Hakan Lindholm [EMAIL PROTECTED] Revision ChangesPath 1.43 +1 -1 apache-1.3/INSTALL Index: INSTALL === RCS file: /export/home/cvs/apache-1.3/INSTALL,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- INSTALL 1998/09/19 13:06:40 1.42 +++ INSTALL 1998/09/28 19:28:01 1.43 @@ -271,7 +271,7 @@ (-) mod_speling .. Correction of misspelled URLs Directory Handling (+) mod_dir .. Directory and directory default file handling - (+) mod_auto_index ... Automated directory index file generation + (+) mod_autoindex Automated directory index file generation Access Control (+) mod_access ... Access Control (user, host, network) (+) mod_auth . HTTP Basic Authentication (user, passwd)
cvs commit: apache-1.3/src/helpers GuessOS
jim 98/09/28 13:04:35
Modified:src CHANGES
src/helpers GuessOS
Log:
Submitted by: Steve Cameron [EMAIL PROTECTED]
Revision ChangesPath
1.1082+5 -2 apache-1.3/src/CHANGES
Index: CHANGES
===
RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v
retrieving revision 1.1081
retrieving revision 1.1082
diff -u -r1.1081 -r1.1082
--- CHANGES 1998/09/26 00:07:06 1.1081
+++ CHANGES 1998/09/28 20:04:33 1.1082
@@ -1,5 +1,8 @@
Changes with Apache 1.3.3
-
+
+ *) PORT: Allow GuessOS to recognize Unixware 7.0.1 [Steve Cameron
+ [EMAIL PROTECTED]]
+
*) Reconstructed the loop through multiple htaccess file names so
that missing files are not confused with unreadable files.
[Roy Fielding]
@@ -7,7 +10,7 @@
*) The ap_pfopen and ap_pfdopen routines were failing to protect the
errno on an error, which leads to one error being mistaken for
another when reading non-existant .htaccess files.
- [Jim Jagielski, Roy Fielding]
+ [Jim Jagielski]
*) OS/2: The new header tests get things right, need to update
ap_config.h. [Brian Havard]
1.47 +5 -3 apache-1.3/src/helpers/GuessOS
Index: GuessOS
===
RCS file: /export/home/cvs/apache-1.3/src/helpers/GuessOS,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- GuessOS 1998/09/16 20:49:23 1.46
+++ GuessOS 1998/09/28 20:04:35 1.47
@@ -53,9 +53,11 @@
echo whatever-whatever-unixware1; exit 0
;;
5)
- if [ x$VERSION = x7 ]; then
- echo ${MACHINE}-whatever-unixware7; exit 0
- fi
+ case $VERSION in
+ 7*)
+ echo ${MACHINE}-whatever-unixware7; exit 0
+ ;;
+ esac
;;
esac
fi
