From: random832@fastmail.com (Random832)
Subject: [TUHS] etymology of cron
Date: Tue, 22 Dec 2015 23:05:57 -0500 [thread overview]
Message-ID: <1450843557.2182645.474607945.01DCBBC4@webmail.messagingengine.com> (raw)
In-Reply-To: <20151223025921.GB9303@mercury.ccil.org>
On Tue, Dec 22, 2015, at 21:59, John Cowan wrote:
> Wikipedia is by nature a *summary of the published literature*. If you
> want to get some folklore, like what "cron" stands for, into Wikipedia,
> then publish a folklore article in a journal, book, or similar reputable
> publication. Random uncontrolled mailing lists simply do not count.
The problem is this backronym is the sort of nonsense that attaches to
_all_ computer commands that are not an English word (and a fair few
that are), and that should heavily weigh against the use of people's
willingness to uncritically repeat them in print as a "reliable source".
It may be reasonable, in Wikipedia's role as a "summary of the published
literature", to say something like "some people have suggested" that it
may be an acronym, and to list the sources there, but certainly _not_ to
assert that it was actually intended as one without a source actually
traceable to someone in a position to know.
next prev parent reply other threads:[~2015-12-23 4:05 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-12-23 4:27 ` John Cowan
2015-12-23 0:46 ` Warren Toomey
2015-12-23 6:47 ` Dave Horsfall
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 13:30 Norman Wilson
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
2015-12-23 14:38 Noel Chiappa
2015-12-23 18:58 ` John Cowan
[not found] <mailman.20.1450886678.3292.tuhs@minnie.tuhs.org>
2015-12-23 17:09 ` Johnny Billquist
2015-12-23 17:19 Norman Wilson
2015-12-23 19:04 ` John Cowan
2015-12-23 19:41 ` SZIGETI Szabolcs
[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
2016-01-02 23:14 Norman Wilson
2016-01-02 23:18 ` Greg 'groggy' Lehey
2016-01-03 14:26 Noel Chiappa
2016-01-13 20:31 Noel Chiappa
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=1450843557.2182645.474607945.01DCBBC4@webmail.messagingengine.com \
--to=random832@fastmail.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).