From: Thomas Sailer <sailer@sailer.dynip.lugs.ch>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: "Curt, WE7U" <archer@eskimo.com>,
"David D. Hagood" <wowbagger@sktc.net>,
linux-hams@vger.kernel.org
Subject: Re: callsign limit
Date: Thu, 01 Jun 2006 21:33:54 +0200 [thread overview]
Message-ID: <1149190435.25319.14.camel@unreal> (raw)
In-Reply-To: <20060601185228.GC10812@linux-mips.org>
On Thu, 2006-06-01 at 19:52 +0100, Ralf Baechle DL5RB wrote:
> Yes and no. I don't think anything tries to follow the new spec to the
> letter but quite a few of it's elements have made it into actual
> implementations.
Or the other way round. Quite a few implementation practices have made
it into the 2.2 spec, without making sure the 2.2 spec is actually
self-consistent.
73 Tom
next prev parent reply other threads:[~2006-06-01 19:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 9:27 callsign limit stephen
2006-05-31 9:37 ` Hamish Moffatt
2006-05-31 11:03 ` Chuck Hast
2006-05-31 11:19 ` Hamish Moffatt
2006-06-01 1:40 ` Ralf Baechle DL5RB
2006-06-01 12:04 ` David D. Hagood
2006-06-01 13:25 ` Ralf Baechle DL5RB
2006-06-01 14:31 ` Curt, WE7U
2006-06-01 15:08 ` Ralf Baechle DL5RB
2006-06-01 15:15 ` Curt, WE7U
2006-06-01 18:52 ` Ralf Baechle DL5RB
2006-06-01 19:33 ` Thomas Sailer [this message]
2006-06-02 2:51 ` Kevin Dawson
2006-06-02 3:47 ` Hamish Moffatt
2006-05-31 13:05 ` Geoff Blake
2006-06-01 10:34 ` stephen
2006-06-01 10:54 ` Chuck Hast
2006-06-01 13:47 ` Hamish Moffatt
2006-06-01 14:00 ` Geoff Blake
2006-05-31 13:02 ` Matti Aarnio
2006-05-31 13:12 ` Thomas Sailer
2006-05-31 14:02 ` Matti Aarnio
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 12:12 IT3 Stuart Blake Tener
2006-05-31 12:41 ` Chuck Hast
2006-05-31 13:15 ` Robert Steinhäußer
2006-05-31 14:57 ` Bob Nielsen
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=1149190435.25319.14.camel@unreal \
--to=sailer@sailer.dynip.lugs.ch \
--cc=archer@eskimo.com \
--cc=linux-hams@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=wowbagger@sktc.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