-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 March 2003 1:28 pm, you wrote:
Curtis, you crack me up! Thanks! I needed a chuckle. This list has become far too serious. There's no reason why we can't deal with the business of the day and have a little levity while doing it. I appreciate it. > lol! > > Partially, my post is self-indicting (although the general mailing list > population may not have noticed it), because of late I have been quickly > spell checking some of my posts, instead of fully proof-reading them, which > creates an end result of properly spelled "the" instead of "then", or other > such marvellous proof reading gems. :-P > > Luckily, we are a Linux User Group, so most of us are probably used to all > manners of man pages, programming code, and international "English". I > mean if you can read RFCs, you shouldn't have any problems understanding > everyone on this list. :-D > > Check out this gem I found a long time ago (from RFC 2136: Dynamic Updates > in the Domain Name System (DNS UPDATE)). > > "The pseudocode used in this document is for example purposes only. > If it is found to disagree with the text, the text shall be > considered authoritative. If the text is found to be ambiguous, the > pseudocode can be used to help resolve the ambiguity." > > Uh-huh. That should clear things up. :-) > > Curtis. > > P.S. For the record, I read this to myself at least twice, so if it's > still a mess it's because I'm hopeless. No flames please. :-D lol - -- Jarrod Major GPG Fingerprint: FA4A 1EA3 A0EE A842 07BB 804C 0090 14F6 BE6E DE3D Registered Linux User: #224211 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQCVAwUBPnjUbACQFPa+bt49AQJ12gQAkY7BKALH1xEhl3+8W5w18uKNMQ6IDYOG 116trRdX1IEVCz6hTiPSAqD+ZVdDS2CMDl0UGjI2GtBNcZ8/p6iHqSQClBUrzNBs cW9819eETXgew0EcaUab523rrdbZnsRwuWMdTj78rz99QqJt5JBv/kEHLexOR4R5 spPfDGSFxWk= =gDIe -----END PGP SIGNATURE-----
