]> granicus.if.org Git - apache/commit
After an install, the default config files are useful. After an upgrade
authorRyan Bloom <rbb@apache.org>
Tue, 23 Jul 2002 17:44:55 +0000 (17:44 +0000)
committerRyan Bloom <rbb@apache.org>
Tue, 23 Jul 2002 17:44:55 +0000 (17:44 +0000)
commit64275b46db8f666cc56396c0b91bf13b41c5c521
tree40ae33aa6e3ab03f9711df68ecb5bf6643772601
parenta9340ff4ca7ed8254608f3ee0eba3fb58e2da7b7
After an install, the default config files are useful.  After an upgrade
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
STATUS