From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Why I've been quiet for a while...
Date: Mon, 8 Jul 2019 19:58:13 -0600 [thread overview]
Message-ID: <9149512a-2ed9-26a4-9c06-9beef58d7a9f@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1907091118070.53965@aneurin.horsfall.org>
On 7/8/19 7:20 PM, Dave Horsfall wrote:
> A combination of both an extended back-hoe fade and me accidentally
> blocking Minnie :-(
Oops!
> (This is also a test to see if I'm still on COFF, as it's a fairly quiet
> list.)
Well, I see your message made it to and through the COFF mailing list on
minnie.
I don't know what your test criteria are to speculate at a pass / fail.
I'll leave that for you to decide.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4008 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20190708/513d3329/attachment.bin>
prev parent reply other threads:[~2019-07-09 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 1:20 dave
2019-07-09 1:58 ` gtaylor [this message]
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=9149512a-2ed9-26a4-9c06-9beef58d7a9f@spamtrap.tnetconsulting.net \
--to=coff@minnie.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).