From: Ian Lance Taylor <ian@zembu.com>
To: jsm@cygnus.com
Cc: gas2@sourceware.cygnus.com, bfd@sourceware.cygnus.com
Subject: Changes in mailing list setup
Date: Thu, 15 Apr 1999 16:36:00 -0000 [thread overview]
Message-ID: <19990415233610.3537.qmail@daffy.airs.com> (raw)
I'd like to publically thank Jason for moving the bfd and gas2 mailing
lists over to sourceware.cygnus.com. Among other things, they should
now be distributed more quickly.
Jason didn't explicitly mention it, but he has moved the old
Cygnus-internal mailing list archives over, so the web interface has a
long history of messages to the lists.
Jason has been doing great work in maintaining sourceware.cygnus.com,
which is used by a number of free software projects. As we all know,
infrastructure tends to be a thankless job. So although tomorrow he
will doubtless return to his obscurity, right now he should bask
briefly in the admiration and gratitude of the 50 or so people who
read these mailing lists.
Cygnus Solutions also deserves our thanks for donating the
sourceware.cygnus.com hardware.
Ian
reply other threads:[~1999-04-15 16:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990415233610.3537.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=bfd@sourceware.cygnus.com \
--cc=gas2@sourceware.cygnus.com \
--cc=jsm@cygnus.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).