From: "Peter C. Norton" <spacey-linux-kernel@lenin.nu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.59 morse code panics
Date: Mon, 3 Feb 2003 22:00:07 -0800 [thread overview]
Message-ID: <20030204060007.GD16814@lenin.nu> (raw)
In-Reply-To: <200301311601.h0VG159O001744@darkstar.example.net>
On Fri, Jan 31, 2003 at 04:01:05PM +0000, John Bradford wrote:
> Especially since a number of Linux developers have ham radio
> experience.
Well most linux users don't. I'm sure its really easy to find a morse
code chart in many hundreds of places online. But 2 scripts - one
that turns keyboard input or mic input into dots and dashes (so you
can enter it yourself or put the phone up to the system's microphone)
would help. Then all you'd need is a morse->ascii converter.
So who's got a good morse->ascii program? And who has the
dot-dash->.-.-.- translator? And the audio->.-.-.- translator?
-Peter
--
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.
Plan 2: If you're going to apologize, don't do it. If you're going to
do it, don't apologize
next prev parent reply other threads:[~2003-02-04 5:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030131104326.GF12286@louise.pinerecords.com.suse.lists.linux.kernel>
[not found] ` <200301311112.h0VBCv00000575@darkstar.example.net.suse.lists.linux.kernel>
[not found] ` <20030131132221.GA12834@codemonkey.org.uk.suse.lists.linux.kernel>
[not found] ` <1044025785.1654.13.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2003-01-31 15:34 ` [PATCH] 2.5.59 morse code panics Andi Kleen
2003-01-31 15:41 ` Tomas Szepe
2003-01-31 16:01 ` John Bradford
2003-01-31 16:11 ` Tomas Szepe
2003-01-31 16:17 ` John Bradford
2003-01-31 19:52 ` Horst von Brand
2003-01-31 20:04 ` John Bradford
2003-01-31 21:08 ` Eric Weigle
2003-01-31 21:14 ` John Bradford
2003-02-02 15:42 ` Bill Davidsen
2003-02-03 19:14 ` Jos Hulzink
2003-02-03 21:29 ` Bill Davidsen
2003-02-04 6:00 ` Peter C. Norton [this message]
2003-02-07 15:51 ` Ryan Anderson
2003-02-07 16:39 ` John Bradford
2003-01-31 15:46 ` Dave Jones
2003-01-31 15:55 ` Valdis.Kletnieks
2003-02-03 15:50 ` Pavel Machek
2003-02-04 16:32 ` Henning P. Schmiedehausen
2003-02-05 17:56 Marcelo Roberto Jimenez
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 21:31 Albert D. Cahalan
2003-01-30 15:07 Tomas Szepe
2003-01-30 17:36 ` Dave Jones
2003-01-30 18:45 ` Alan Cox
2003-01-31 10:43 ` Tomas Szepe
2003-01-31 11:12 ` John Bradford
2003-01-31 13:22 ` Dave Jones
2003-01-31 14:40 ` Valdis.Kletnieks
2003-01-31 14:58 ` John Bradford
2003-01-31 15:05 ` Dave Jones
2003-01-31 15:32 ` Valdis.Kletnieks
2003-01-31 15:09 ` Alan Cox
2003-01-31 14:29 ` John Bradford
2003-01-31 15:13 ` Dave Jones
2003-01-31 15:12 ` Dave Jones
2003-01-31 15:27 ` John Bradford
2003-01-31 15:21 ` Scott Robert Ladd
2003-01-31 17:59 ` Vojtech Pavlik
2003-01-31 18:06 ` Tomas Szepe
2003-01-31 19:38 ` Tomas Szepe
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=20030204060007.GD16814@lenin.nu \
--to=spacey-linux-kernel@lenin.nu \
--cc=linux-kernel@vger.kernel.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