From: Andrew Hume <andrew@humeweb.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Office Automation System (OAS)?
Date: Sun, 11 Dec 2022 22:38:52 -0800 [thread overview]
Message-ID: <525C07D4-84A7-4848-AF9D-C49E22432563@humeweb.com> (raw)
In-Reply-To: <20221211174007.5BEA721FDD@orac.inputplus.co.uk>
regrettably, i do not recall this.
as far as i could guess,i simply went with a short name
and most likely e stood for editor.
> On Dec 11, 2022, at 9:40 AM, Ralph Corderoy <ralph@inputplus.co.uk> wrote:
>
> Hi andrew,
>
>> i wrote ef.
>
> Was its name from ed → ee → ef or something else?
>
> --
> Cheers, Ralph.
next prev parent reply other threads:[~2022-12-12 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 20:24 [TUHS] " segaloco via TUHS
2022-12-08 21:03 ` [TUHS] " Andrew Hume
2022-12-11 17:40 ` Ralph Corderoy
2022-12-12 6:38 ` Andrew Hume [this message]
2022-12-12 16:10 ` segaloco via TUHS
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=525C07D4-84A7-4848-AF9D-C49E22432563@humeweb.com \
--to=andrew@humeweb.com \
--cc=ralph@inputplus.co.uk \
--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).