This is fixed in versio 2.4
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/239048
Title:
apache2 conf.d and
This is fixed in versio 2.4
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/239048
Title:
apache2 conf.d and sites-enabled oops
RCS encourages one to put its files in a directory named RCS -
otherwise, they clutter up the original directory with near-matches for
every controlled file.
Prefixing the directory with a dot seems like a good plan. Somehow, I
doubt the CVS community would be open to that change. I suspect the
RCS encourages one to put its files in a directory named RCS -
otherwise, they clutter up the original directory with near-matches for
every controlled file.
Prefixing the directory with a dot seems like a good plan. Somehow, I
doubt the CVS community would be open to that change. I suspect the
Most current version control systems (like SVN, git, hg) use files or
dirs starting with a dot to store their data. These files are already
ignored. The same is true for RCS because the filenames contain a comma.
CVS is the only VCS I know that does not use special chars in its file
name. We could
Thanks for the bug report. This will be considered for intrepid.
chuck
** Changed in: apache2 (Ubuntu)
Status: New = Triaged
--
apache2 conf.d and sites-enabled oops
https://bugs.launchpad.net/bugs/239048
You received this bug notification because you are a member of Ubuntu
Bugs, which
Update: Checking my config history, this was not introduced when I
thought it was. I merely hadn't restarted apache after putting
everything in version control.
The base principle still applies: one should not have the default
configuration preclude revision control. Checking on things further,
Update: Checking my config history, this was not introduced when I
thought it was. I merely hadn't restarted apache after putting
everything in version control.
The base principle still applies: one should not have the default
configuration preclude revision control. Checking on things further,
