public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason@molenda.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@sourceware.org
Subject: Re: sourceware.org
Date: Wed, 21 Nov 2001 14:05:00 -0000	[thread overview]
Message-ID: <20011121220528.A1135@molenda.com> (raw)
Message-ID: <20011121140500.WJhqqDU_PCyi8HEep3OAZ5nyWSeQ3bCnWOsZFn3pa4w@z> (raw)
In-Reply-To: <si1yirssov.fsf@daffy.airs.com>

On Wed, Nov 21, 2001 at 01:46:40PM -0800, Ian Lance Taylor wrote:
> I noticed that the domain name sourceware.org was available.  

Sweet!  I've been meaning to look at the status of Sourceware for
a little while now.  Back in '98 or '99 there was some l0zers who'd
purchased the trademark rights are were telling us to stop using
the name (which I essentially ignored :-) - I'm positive their
company doesn't exist any longer.  It sounded implausible even in
the silly high-times of 1999-2000.

The whois record for sourceware.com shows the owner bought it for
five years.  Boo!  It looks like a single person doing some side
work out of his home.

J

  reply	other threads:[~2001-11-21 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 17:15 sourceware.org Ian Lance Taylor
2001-10-23 18:19 ` Jason Molenda [this message]
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=20011121220528.A1135@molenda.com \
    --to=jason@molenda.com \
    --cc=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).