From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Too important
Date: Sat, 22 May 2021 15:52:29 -0600 [thread overview]
Message-ID: <af60d7f7-7f78-b650-c04d-2c40a6f7d668@SystematicSw.ab.ca> (raw)
In-Reply-To: <SCslVpYNMmEO6TtUpcXQ3R3cve1F13Rk9mKvB95z4@localhost.localdomain>
Seems to me somebody needs to bump up the spam milters to high!
A number of useful terms to add are included in the original email.
On 2021-05-22 12:40, Noland wrote:
...<SPAM EXTORTION ATTEMPTS>...
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
parent reply other threads:[~2021-05-22 21:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SCslVpYNMmEO6TtUpcXQ3R3cve1F13Rk9mKvB95z4@localhost.localdomain>]
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=af60d7f7-7f78-b650-c04d-2c40a6f7d668@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).