cvs commit: apache-1.3 STATUS

2000-01-08 Thread jim
jim 00/01/08 06:41:20

  Modified:.STATUS
  Log:
  Some updates. Before we release I'd like for us
  to look at these 2 additions. The HPUX problem I consider a
  show-stopper (it was before). Randy, can you confirm that
  the builds are broken?
  
  Revision  ChangesPath
  1.778 +16 -4 apache-1.3/STATUS
  
  Index: STATUS
  ===
  RCS file: /export/home/cvs/apache-1.3/STATUS,v
  retrieving revision 1.777
  retrieving revision 1.778
  diff -u -r1.777 -r1.778
  --- STATUS2000/01/06 17:02:58 1.777
  +++ STATUS2000/01/08 14:41:19 1.778
  @@ -1,5 +1,5 @@
 1.3 STATUS:
  -  Last modified at [$Date: 2000/01/06 17:02:58 $]
  +  Last modified at [$Date: 2000/01/08 14:41:19 $]
   
   Release:
   
  @@ -25,15 +25,27 @@
   
   RELEASE SHOWSTOPPERS:
   
  -
  -RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
  -
   * HPUX binary build failure due to the fact that it is building
 libstandard.a and adding .so objects to the libstandard.a starting
 with mod_vhost_alias.so.
   Message-ID: [EMAIL PROTECTED]
Status: Randy committed a temporary fix
  + UPDATE: Keith Wannamaker reports that Ralf's patch to
  + fix PR4974 has broken this again. Please see:
  +   [EMAIL PROTECTED]
  +
  +RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
   
  +* Cliff Woolley suggests the following patch to fix a problem
  +  with using mod_status and mod_vhost_alias. At issue is the
  +  fact that because mod_vhost_alias does not create actual
  +  vhost structures, the server-name reported in mod_status
  +  is incorrect. The patch reverts to the old behavior of
  +  storing the server-name of the request as a string in
  +  scoreboard.
  +Message-ID: [EMAIL PROTECTED]
  + Status: Jim -0
  +  
   * long pathnames with many components and no AllowOverride None
 Workaround is to define Directory / with AllowOverride None,
 which is something all sites should do in any case.
  
  
  


cvs commit: apache-1.3/htdocs/manual/misc rewriteguide.html

2000-01-08 Thread rse
rse 00/01/08 06:50:16

  Modified:src  CHANGES
   htdocs/manual index.html
   htdocs/manual/mod mod_rewrite.html
  Added:   htdocs/manual/misc rewriteguide.html
  Log:
  Make our nitpicking and complaining guys happy:
  
  Added the mod_rewrite `URL Rewriting Guide' to the online documentation
  (htdocs/manual/misc/rewriteguide.html). This paper provides a large
  collection of practical solutions to URL based problems a webmaster is
  often confronted with.
  
  This version of the text was translated from my WML source on my website
  and my old official version is now discarded. So, as it was requested,
  this can be treated as an official donation of this text to the ASF.
  This way the ASF is now the official owner of this text.
  
 - - -
  
  IRONIC
  Be happy and give Ken and Jim the credit for achieving this by being
  such sensitive and friendly to other developers like me and always
  reminding us that it is such contemptuous to implicitly promote ones
  name by writing free software and contributing to projects like Apache.
  Sorry that I have forgotten to donate this piece of text to the ASF in
  the past and instead added such a contemptible hyperlink directing to a
  page on www.engelschall.com. I hope this is now fixed and the closed and
  holy ASF world is rescued again.
  /IRONIC
  
  PERSONAL
  I think, I don't have to say that I'm more than angry and disappointed
  how developers like me are constantly bashed in the ASF... we can go for
  it also in the future, but we should stop looking astonished all the
  time if we find out that too less people contribute to the ASF and old
  developers like me no longer have a warm feeling here, please. It's our
  own fault in thinking that contributions are for free and anonymous just
  because our project is a group effort.
  
  IMHO we already have forgotten the golden rule of Open Source
  development: if one wants happy and long-term contributing developers
  one especially has to make sure they receive the requested credit.
  There is an upper limit a project can accept to give, of course. But
  credit always has to depend on the amount, quality _and_ duration of
  contribution and IMHO cannot be judged by stating that just all people
  are equal and so some contributors can be bashed for the fact that their
  name occurs more often.
  
  It is correct that my name occurs more often caused by the fact that I
  always try to bring in my stuff to the project. But keep in mind that
  this is because I _HAVE_ stuff to bring in which I've created _OUTSIDE_
  the project. So I think its unfair to bash me just because I try harder
  to bring in my additional stuff. If a developer has not much externally
  created stuff, he cannot bring it in to the project, of course. But just
  because one has more externally created stuff and tries to bring it in,
  is IMHO no reason and excuse to bash him for this. It's not my fault
  that I write in my freetime more Open Source packages like most of you.
  
  So if you dislike stuff developers want to bring in, decide on the
  contribution based on fair technical arguments (pros and cons). But
  don't judge the contributions all the time just because you think this
  way you promote someone (be it RSE, GNU or whoever else). Hell, an
  Open Source project is not a group of people to rule their own closed
  world and be celebrated in the press for this. It's still an effort to
  create the best piece of _software_ money can't buy. So you should stop
  thinking about contributors as our enemy. They are the main driving
  force of every project, although some people seem to not understand
  this at all. And whatever you think about my personal opinion, but
  IMHO it's not bad for a project if someone's name is promoted with
  it, too. What is actually bad are those complains and discussions
  which make developers angry and the fact that they result in even less
  contributions.
  /PERSONAL
  
  Revision  ChangesPath
  1.1489+6 -0  apache-1.3/src/CHANGES
  
  Index: CHANGES
  ===
  RCS file: /home/cvs/apache-1.3/src/CHANGES,v
  retrieving revision 1.1488
  retrieving revision 1.1489
  diff -u -r1.1488 -r1.1489
  --- CHANGES   2000/01/01 17:07:32 1.1488
  +++ CHANGES   2000/01/08 14:50:05 1.1489
  @@ -1,5 +1,11 @@
   Changes with Apache 1.3.10
   
  +  *) Added the mod_rewrite `URL Rewriting Guide' to the online
  + documentation (htdocs/manual/misc/rewriteguide.html). This paper
  + provides a large collection of practical solutions to URL based
  + problems a webmaster is often confronted with.
  + [Ralf S. Engelschall]
  +
 *) Add a suexec status report to the '-l' (compiled-in modules)
output. [Ken Coar]
   
  
  
  
  1.30  +1 -0  apache-1.3/htdocs/manual/index.html
  
  Index: index.html
  

cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html

2000-01-08 Thread lars
lars00/01/08 11:57:30

  Modified:htdocs/manual/mod mod_mime.html
  Log:
  add missing compatiblity info
  
  Revision  ChangesPath
  1.34  +6 -1  apache-1.3/htdocs/manual/mod/mod_mime.html
  
  Index: mod_mime.html
  ===
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- mod_mime.html 1999/12/09 18:10:39 1.33
  +++ mod_mime.html 2000/01/08 19:57:29 1.34
  @@ -397,7 +397,12 @@
   A
HREF=directive-dict.html#Module
REL=Help
  -STRONGModule:/STRONG/A mod_mimeP
  +STRONGModule:/STRONG/A mod_mimeBR
  +A
  + HREF=directive-dict.html#Compatibility
  + REL=Help
  +STRONGCompatibility:/STRONG/A DefaultLanguage is only available in 
Apache
  +1.3.4 and later.P
   
   The DefaultLanguage directive tells Apache that all files in the
   directive's scope (EMe.g./EM, all files covered by the current