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: Wed, 23 Apr 2003 18:28:00 -0000 [thread overview]
Message-ID: <3EA6DB51.4040307@jifvik.org> (raw)
In-Reply-To: <m3d6jdm61v.fsf@gossamer.airs.com>
Wow, super speedy turnaround, thanks!
Ian Lance Taylor wrote:
> Jonathan Larmour <jifl@jifvik.org> writes:
>>That along with
>>recognising ecos.sourceware.org in the s.r.c web server as a virtual
>>host going to /ecos/ ?
>
>
> Done. Note that the GIF is broken on ecos.sourceware.org, though it
> works on sourceware.org/ecos, because the IMG SRC uses an absolute
> path. There may be other similar problems.
Probably, but now we'll be able to find them more easily :-).
> I kept the same CustomLog and ErrorLog, as was also done by some of
> the other virtual hosts. However, the current log format does not
> indicate which host was requested. I recommend adding %v at the start
> of the `combined' LogFormat line in httpd.conf, which will put the
> virtual host at the start of each line. However, I didn't want to do
> that without checking with other people.
It will make log analysis difficult for those who do that certainly, but
changing the format will also do that.
>>Finally, could someone set up the ecos-bugs mailing list slightly
>>differently.... right now it's set up only to receive mail from
>>bugzilla@redhat.com. However due to unfortunate unresponsiveness by
>>the bugzilla.redhat.com maintainer I've finally given up with this
>>approach :-|. So instead could that restriction be temporarily
>>removed? A bit later I'll want something like
>>bugzilla-admin-daemon@ecoscentric.com to replace it, but not yet to be
>>sure there aren't any teething troubles.
>
>
> I commented out the line in ~alias/.qmail-ecos-bugs which I believe
> was enforcing this restriction. I haven't tested it.
It appears to work fine, thanks.
>>If there's any way I could help (e.g. by "borrowing" root to save you
>>guys time) then please just say. I don't want to cause you all hassle!
>
> As they say, lend somebody root for five minutes, and they have it for
> all eternity.
Heh :-).
Thanks again,
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-04-23 18:28 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 [this message]
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
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=3EA6DB51.4040307@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).