From: Brandon Black photon@nol.net
Subject: effort duplication....
Date: Sun, 17 Nov 1996 19:27:43 -0600 [thread overview]
Message-ID: <19961118012743.flYWz-VCXrFGueLZlHU-HZjjvWBRf8LVRpwyO1iMrvM@z> (raw)
Along the lines of the "effort duplication" problem.. I have a few other
wishlist items which I've been considering trying to work on (some are
hopelessly beyond my skill level though)...
An audio CD player...
Terminal emulators like the hp2621 one, for more common term types like
vt10[02], vt220, xterm, etc...
drivers for some popular PCI FDDI cards... Fast Ethernet cards would be
nice too, but FDDI is of course much better :)
Maybe it would make all of this easier and encourage people a little more
if someone were to set up a "project registry" of who is working on what,
and what the status of their project is... make it easy to see if
something you were thinking about is already in the works, and who's doing
it. All it would take is a concise one-entry-per-line text file
maintained on an ftp site by someone who has a few minutes left over each
day.
next reply other threads:[~1996-11-18 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-18 1:27 Brandon [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-11-17 23:29 Scott
1996-11-17 21:04 Russ
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=19961118012743.flYWz-VCXrFGueLZlHU-HZjjvWBRf8LVRpwyO1iMrvM@z \
--to=9fans@9fans.net \
/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 NNTP newsgroup(s).