From: Ian Lance Taylor <ian@airs.com>
To: overseers@sourceware.org
Subject: sourceware.org
Date: Mon, 22 Oct 2001 17:15:00 -0000 [thread overview]
Message-ID: <si1yirssov.fsf@daffy.airs.com> (raw)
I noticed that the domain name sourceware.org was available. For my
own amusement, I bought it, and pointed it at sources.redhat.com. You
can now look at http://sourceware.org/ and http://www.sourceware.org/.
You can also send mail @sourceware.org.
sourceware.com is not, alas, available.
Ian
WARNING: multiple messages have this Message-ID
From: Ian Lance Taylor <ian@airs.com>
To: overseers@sourceware.org
Subject: sourceware.org
Date: Wed, 21 Nov 2001 13:46:00 -0000 [thread overview]
Message-ID: <si1yirssov.fsf@daffy.airs.com> (raw)
Message-ID: <20011121134600.nkIjCODcMywamPuUUg2xTSIII6znMT9iOUzKFYLu1oI@z> (raw)
I noticed that the domain name sourceware.org was available. For my
own amusement, I bought it, and pointed it at sources.redhat.com. You
can now look at http://sourceware.org/ and http://www.sourceware.org/ .
You can also send mail @sourceware.org.
sourceware.com is not, alas, available.
Ian
next reply other threads:[~2001-11-21 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 17:15 Ian Lance Taylor [this message]
2001-10-23 18:19 ` sourceware.org Jason Molenda
2001-10-25 16:39 ` sourceware.org Christopher Faylor
2001-11-21 17:11 ` sourceware.org Christopher Faylor
2001-11-21 14:05 ` sourceware.org Jason Molenda
2001-10-23 19:37 ` sourceware.org Per Bothner
2001-10-24 8:32 ` sourceware.org Ian Lance Taylor
2001-11-21 14:45 ` sourceware.org Ian Lance Taylor
2001-11-21 14:20 ` sourceware.org Per Bothner
2001-11-21 13:46 ` sourceware.org Ian Lance Taylor
2003-03-04 15:41 sourceware.org Jonathan Larmour
2003-03-05 2:52 ` sourceware.org Christopher Faylor
2003-03-05 6:42 ` sourceware.org Jason Molenda
2003-03-05 7:14 ` sourceware.org Phil Edwards
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=si1yirssov.fsf@daffy.airs.com \
--to=ian@airs.com \
--cc=overseers@sourceware.org \
/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).