The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: Adam Sampson <ats@offog.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Bringing a Chainsaw
Date: Sat, 10 Dec 2022 12:15:24 -0500	[thread overview]
Message-ID: <CALQ0xCC34kmaknZwHABP9SwPhA7+r-Qc5j9of0EL8qQ3-hYBqg@mail.gmail.com> (raw)
In-Reply-To: <y2aa63vxkqy.fsf@offog.org>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

Mike is an old friend ... I will send him a copy of "Bringing a Chainsaw"
and ask ... I don't think he was in Yorktown at the time but I probably
told him about the work while it was happening.
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>


On Sat, Dec 10, 2022 at 11:56 AM Adam Sampson <ats@offog.org> wrote:

> John Cowan <cowan@ccil.org> writes:
>
> > Some editions of the Jargon File contain an entry for _branch to
> > Fishkill_, defined as "Any unexpected jump in a program that produces
> > catastrophic or just plain weird results" and attributed to IBM.
>
> Mike Cowlishaw's IBM Jargon and General Computing Dictionary, Tenth
> Edition <http://www.comlay.net/ibmjarg.pdf> was probably the source for
> this -- it includes both "branch to Fishkill" and "branch to Owego" with
> exactly this definition.
>
> --
> Adam Sampson <ats@offog.org>                         <http://offog.org/>
>

[-- Attachment #2: Type: text/html, Size: 1896 bytes --]

  reply	other threads:[~2022-12-10 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 21:49 [TUHS] " Marc Donner
2022-12-09 22:49 ` [TUHS] " Rich Morin
2022-12-10  6:54 ` John Cowan
2022-12-10  9:10   ` Marc Donner
2022-12-10 16:54   ` Adam Sampson
2022-12-10 17:15     ` Marc Donner [this message]
2022-12-11 22:23       ` Marc Donner
2022-12-11 22:47         ` John Cowan
2022-12-11 22:50           ` Marc Donner
2022-12-12  1:32             ` John Cowan

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=CALQ0xCC34kmaknZwHABP9SwPhA7+r-Qc5j9of0EL8qQ3-hYBqg@mail.gmail.com \
    --to=marc.donner@gmail.com \
    --cc=ats@offog.org \
    --cc=tuhs@tuhs.org \
    /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).