From: Jonathan Larmour <jifl@jifvik.org>
To: overseers@sources.redhat.com
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: ecos.sourceware.org and mailing list request
Date: Wed, 23 Apr 2003 17:30:00 -0000 [thread overview]
Message-ID: <3EA6CD95.1080509@jifvik.org> (raw)
Hi guys,
Another couple of favours to ask of those who have the root runes of
power... but especially Ian as he is the owner of sourceware.org...
Would it be possible to add ecos.sourceware.org as a subdomain/host and
pointing at sources.redhat.com's IP address? That along with recognising
ecos.sourceware.org in the s.r.c web server as a virtual host going to
/ecos/ ?
Similarly underneath that could we have bugs.ecos.sourceware.org as a
CNAME pointing at bugzilla.ecoscentric.com please?
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.
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!
Thanks!
Jifl
--
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next reply other threads:[~2003-04-23 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 17:30 Jonathan Larmour [this message]
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
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=3EA6CD95.1080509@jifvik.org \
--to=jifl@jifvik.org \
--cc=ecos-maintainers@sources.redhat.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).