Skip to content
  1. Jul 26, 2002
  3. Jul 25, 2002
  5. Jul 24, 2002
  7. Jul 23, 2002
    • Greg Ames's avatar
      vote on wrapper scripts · 21dc04d1
      Greg Ames authored 
      Keeping apachectl simple seems desirable.  The tasks listed for httpd.sh
seem reasonable too.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96160 13f79535-47bb-0310-9956-ffa450edef68
      21dc04d1
    • Joshua Slive's avatar
      Nothing to see here. Just committing a very small change to the transformations. · f0b73da3
      Joshua Slive authored 
      
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96159 13f79535-47bb-0310-9956-ffa450edef68
      f0b73da3
    • Joshua Slive's avatar
      Introduce changes necessary to bring the remainder of the manual into xml. · f810ccbc
      Joshua Slive authored 
      1. Add a <relative-path href="whatever"/> element to the manualpage
DTD.  This should give the path from the location of the page to
the root of the manual directory.  It is necessary for proper linking
to directives, etc.

2. Add the stuff to common.xsl necessary to transform a <manualpage>.
This is basically the minimum.  It creates something VERY similar to
what we had before (with the exception of a little css here and
there).  I very much hope that this will be improved soon to look
nicer.

3. Add configuring.xml, which was written by Astrid Kessler.  I made only
a very few small changes to bring it in line with the current DTD.

I have not yet committed the corresponding configuring.html.en, since I
want to give people a little opporunity to comment on this stuff.

My appologies, but I am committing a few style changes to common.xsl
along with the substantial changes.  That file is really hard to
work with, and should probably be broken up.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96158 13f79535-47bb-0310-9956-ffa450edef68
      f810ccbc
    • Ryan Bloom's avatar
      After an install, the default config files are useful. After an upgrade · 64275b46
      Ryan Bloom authored 
      they aren't.

If the config directive's syntax changed, Apache will tell
you which one changed, and the docs are a better place to go for details
then the default config files.  BTW, the syntax of a directive hasn't
changed for a VERY long time.

If the semantics changed, then nobody will ever know that they need to
look in the default config files to determine that they semantics changed,
because there is no error message.

The argument that you want to be able to get the defaults back doesn't
hold water, because 99.9% of all admins backup their files before
modifying them.  If you aren't backing them up, then that is your problem.

The argument that you may not have a full config directory also doesn't
hold water, because the assumption is that the conf/ directory is coming
from a working server.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96157 13f79535-47bb-0310-9956-ffa450edef68
      64275b46