The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] etymology of cron
Date: Thu, 24 Dec 2015 10:49:39 +1100	[thread overview]
Message-ID: <20151223234939.GL14449@eureka.lemis.com> (raw)
In-Reply-To: <20151223160436.GB6677@mercury.ccil.org> <20151223133603.B1BFE440AE@lignose.oclsc.org>

On Wednesday, 23 December 2015 at 11:04:36 -0500, John Cowan wrote:
> Norman Wilson scripsit:
>
>> But I'd be satisfied if we could somehow stamp out the use of spurious
>> references to support spurious claims.

It occurs to me that there's a difference between stamping out the use
and stamping out the reference.  True story (at some level of truth):

  In the late 18th century a member of a European exploratory mission
  in Australia sees a strange animal jumping around.  He turns to the
  aboriginal guard assigned to him and says "What's that animal?".
  Guard answers: "kangaroo" ("I don't understand what you're saying").

  I've always taken this one to be a joke, but the Oxford English
  Dictionary picks it up and says:

    The common assertion that it really means 'I don't understand'
    (the supposed reply of the local to his questioner) seems to be of
    recent origin and lacks confirmation. (See Morris Austral English
    s.v.)

  And maybe this is the correct way to handle those references.
  Mention them and observe that they lack any substantiation.

> I suppose you could get the original author(s) to print a retraction.

I've been trying to find Phil Diacono, of whom you wouldn't expect
many falso positives, but in fact there are two or three in Melbourne
alone, none of whom seem to be the right one.

In the meantime, help has come from an unlikely direction.  As far as
I can tell, it's nobody on this list, but there's no account behind
the commit, just the IP address 2601:647:4001:bc00:c48d:fc08:b94c:dec2

It refers to an article by Kah Seng Tay at
https://www.quora.com/What-is-the-etymology-of-cron , which appears
undated (date "Wed"), but which goes into more detail and includes a
copy of a message from Brian with essentially the same content as the
one he sent to Doug.  I've updated the page to note lack of
substatiation in the alternative references.

We're not done yet.  Tedickey has once again tagged the entry with
WP:RS.  So a published document would still be a good idea.

wkt: is it time for an informal "Proceedings of TUHS"?

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151224/db6b908d/attachment.sig>


  parent reply	other threads:[~2015-12-23 23:49 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 13:36 Norman Wilson
2015-12-23 13:53 ` Clem Cole
2015-12-24 15:01   ` Clem Cole
2015-12-24 15:17     ` John Cowan
2015-12-24 23:05       ` Greg 'groggy' Lehey
2015-12-25  0:52         ` scj
2015-12-25  1:05           ` Larry McVoy
2015-12-25  2:07             ` Greg 'groggy' Lehey
2015-12-25  2:28               ` Dave Horsfall
2015-12-25 16:21           ` Marc Rochkind
2015-12-23 16:04 ` John Cowan
2015-12-23 23:49 ` Greg 'groggy' Lehey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-13 20:31 Noel Chiappa
2016-01-03 14:26 Noel Chiappa
2016-01-02 23:14 Norman Wilson
2016-01-02 23:18 ` Greg 'groggy' Lehey
     [not found] <mailman.1.1451005554.3365.tuhs@minnie.tuhs.org>
2015-12-25 18:41 ` David
2015-12-25 20:46   ` Marc Rochkind
2015-12-25 22:22   ` Greg 'groggy' Lehey
2016-01-02 19:56     ` Marc Rochkind
2016-01-02 21:06       ` Clem Cole
2016-01-02 22:22       ` Greg 'groggy' Lehey
2016-01-03  1:26         ` Ronald Natalie
2016-01-03 10:30           ` Jacob Goense
2016-01-03 15:32             ` Ronald Natalie
2016-01-03 18:00               ` John Cowan
2016-01-03 12:10           ` Jacob Goense
2016-01-03 15:22             ` Ronald Natalie
2016-01-13 19:48               ` Jeremy C. Reed
2016-01-13 20:02                 ` Ronald Natalie
2016-01-04  2:26           ` Kurt H Maier
2015-12-23 17:19 Norman Wilson
2015-12-23 19:04 ` John Cowan
2015-12-23 19:41 ` SZIGETI Szabolcs
     [not found] <mailman.20.1450886678.3292.tuhs@minnie.tuhs.org>
2015-12-23 17:09 ` Johnny Billquist
2015-12-23 14:38 Noel Chiappa
2015-12-23 18:58 ` John Cowan
2015-12-23 13:30 Norman Wilson
2015-12-23  1:44 Norman Wilson
2015-12-23  2:07 ` Lyndon Nerenberg
2015-12-23  2:19   ` Milo Velimirovic
2015-12-23  2:27     ` Lyndon Nerenberg
2015-12-23  2:36       ` Greg 'groggy' Lehey
2015-12-23  4:53 ` Larry McVoy
2015-12-23 13:45   ` Clem Cole
2015-12-23  0:27 Doug McIlroy
2015-12-23  0:40 ` Greg 'groggy' Lehey
2015-12-23  1:11   ` John Cowan
2015-12-23  1:59     ` Greg 'groggy' Lehey
2015-12-23  2:01       ` David Ryskalczyk
2015-12-23  2:14         ` Greg 'groggy' Lehey
2015-12-23  2:32           ` jason-tuhs
2015-12-23  2:44             ` Lyndon Nerenberg
2015-12-23  2:59             ` John Cowan
2015-12-23  4:05               ` Random832
2015-12-23  4:27                 ` John Cowan
2015-12-23  0:46 ` Warren Toomey
2015-12-23  6:47 ` Dave Horsfall

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=20151223234939.GL14449@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).