From: Sebastien Huet <linuxemb@linux-embedded.com>
To: linux-embedded@waste.org
Cc: linuxce-devel@linuxce.org, linuxppc-embedded@lists.linuxppc.org,
elix@sourceware.cygnus.com, nanogui@linuxhacker.org,
rick@linuxdevices.com, steve@blast.com,
linuxce-devel@linuxce.org
Subject: [OT] linuxembedded domain names to sell.
Date: Tue, 22 Aug 2000 03:58:00 -0000 [thread overview]
Message-ID: <39A25D32.827DA49B@linux-embedded.com> (raw)
Hi,
Due to a lack of time i have to resign from maintaining
http://linux-embedded.org .
The following domain names are to sell
http://linux-embedded.com , net, org
http://linuxembedded.com , net, org
Conditions:
Buyer should be a known participant of the embedded linux community.
Price:
To the highest bidder.
Part of the money will return to the community by supporting projects.
next reply other threads:[~2000-08-22 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 3:58 Sebastien Huet [this message]
2000-08-22 14:01 ` roger Irwin
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=39A25D32.827DA49B@linux-embedded.com \
--to=linuxemb@linux-embedded.com \
--cc=elix@sourceware.cygnus.com \
--cc=linux-embedded@waste.org \
--cc=linuxce-devel@linuxce.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nanogui@linuxhacker.org \
--cc=rick@linuxdevices.com \
--cc=steve@blast.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).