From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>,
"Watson,
Christian M. (GRC-V000)[Peerless Technologies Corp.]"
<christian.m.watson@nasa.gov>,
"Pesich, Justin M. (GRC-LTF0)" <justin.m.pesich@nasa.gov>
Subject: Re: Country Of Origin Verification - 8944
Date: Sun, 14 Jun 2020 11:43:50 -0400 [thread overview]
Message-ID: <20200614154350.GA8121@cgf.cx> (raw)
In-Reply-To: <c145e5f8-7647-e352-1aec-55ec3ce6663f@SystematicSw.ab.ca>
On Thu, Jun 11, 2020 at 11:24:09AM -0600, Brian Inglis wrote:
>On 2020-06-11 10:07, Watson, Christian M. (GRC-V000)[Peerless Technologies
>Corp.] via Cygwin wrote:
>> My name is Christian Watson and I am a Supply Chain Risk Management Coordinator at NASA Glenn Research Center As such, I ensure that all NASA Headquarter IT purchase requests comply with Section 514 of the Consolidated Appropriations Act, 2018, Public Law 115-141 (amended), enacted February 28, 2018. To do so, the country of origin information must be obtained from the company that develops, produces, manufactures, or assembles the product(s). Specifically, identify the country where each of the following products were developed, manufactured, and assembled:
>>
>> * TightVNC 2.8.27
>>
>> Additionally, if the country of origin is outside the United States, please provide any information you may have stating that testing is performed in the United States prior to supplying products to customers.
>> Lastly, if available, please identify all authorized distributors of the product in question.
>
>This is the second email like this you have sent to the Cygwin mailing list:
>if you are going to send a bunch of these to the Cygwin mailing list, you should
>save yourself time and energy, and list all the Cygwin packages in one email,
>which may receive no response, unless you are spam blocked.
^^^^^^^^^^^^^^^^^^^^^^^^^^^
...which is a very good possibility if this proves to be write-only email.
cgf
next prev parent reply other threads:[~2020-06-14 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:07 Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-11 17:24 ` Brian Inglis
2020-06-14 15:43 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-11 15:59 Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-11 17:19 ` Brian Inglis
2020-06-18 3:16 ` Brian Inglis
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=20200614154350.GA8121@cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--cc=christian.m.watson@nasa.gov \
--cc=cygwin@cygwin.com \
--cc=justin.m.pesich@nasa.gov \
/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).