-------- In message <[email protected]>, Attila Kinali writes: >On Sun, 20 Aug 2017 11:28:17 +0000
>> [1] I've always wondered about that rule and I suspect it is a >> mistake. Knowing who is on this list, I imagine that the next >> revision will read the far more sensible: "Non-rubidium *or* >> having ..." > >Yes, singling out Rubidium is kind of weird. I see that rule as a way to carve out telco-class rubidiums, and that's why I think "or" would make much more sense than "and". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
