From: Jonathan Larmour <jifl@jifvik.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@sources.redhat.com,
eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: ecos.sourceware.org and mailing list request
Date: Thu, 01 May 2003 02:24:00 -0000 [thread overview]
Message-ID: <3EB08553.8000604@jifvik.org> (raw)
In-Reply-To: <m3d6jdm61v.fsf@gossamer.airs.com>
Ian Lance Taylor wrote:
>
> Please let us know about any problems. Other overseers, please let me
> know if I messed something out.
Sorry to be a pain but it needs a couple of fixes. To ensure consistent
use of the name, we'd need the faq-o-matic and mailing list archives to be
available there. This should just be a case of adding the following lines
inside the VirtualHost block for ecos.sourceware.org (inspired by other
configs there):
RedirectMatch permanent ^/ml/$ http://ecos.sourceware.org/intouch.html
RedirectMatch permanent ^/ml$ http://ecos.sourceware.org/intouch.html
Alias /ml/ /var/www/sourceware/ml/
Alias /fom-serv/ /sourceware/faq-o-matic/fom-serv/
Alias /htdig/ /var/www/sourceware/htdocs/htdig/
Alias /img/ /var/www/sourceware/htdocs/img/
AliasMatch ^/ecos/(.*) /var/www/sourceware/htdocs/ecos/$1
ScriptAlias /cgi-bin/ /var/www/sourceware/cgi-bin/
ScriptAlias /fom/ /sourceware/faq-o-matic/cgi-bin/
Also since it seems peopled have now resolved to separate out the logs to
a CustomLog for each virtual host, that could be done too.
Jifl
--
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2003-05-01 2:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 17:30 Jonathan Larmour
2003-04-23 18:18 ` Ian Lance Taylor
2003-04-23 18:28 ` Jonathan Larmour
2003-04-23 19:27 ` Christopher Faylor
2003-04-23 20:51 ` Ian Lance Taylor
2003-04-23 21:07 ` Christopher Faylor
2003-04-23 22:19 ` Jason Molenda
2003-05-01 2:24 ` Jonathan Larmour [this message]
2003-05-01 6:33 ` Ian Lance Taylor
2003-05-01 22:29 ` Jonathan Larmour
2003-05-01 22:37 ` Ian Lance Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB08553.8000604@jifvik.org \
--to=jifl@jifvik.org \
--cc=ecos-maintainers@sources.redhat.com \
--cc=ian@airs.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).