public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: "Watson,
	Christian M. (GRC-V000)[Peerless Technologies Corp.]"
	<christian.m.watson@nasa.gov>,
	cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: Country Of Origin Verification - 8944
Date: Wed, 17 Jun 2020 21:04:36 +0300	[thread overview]
Message-ID: <625906552.20200617210436@yandex.ru> (raw)
In-Reply-To: <BY5PR09MB4993965728DECF9AC273DAF2BB9A0@BY5PR09MB4993.namprd09.prod.outlook.com>

Greetings, Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]!

> We appreciate the reply. We are looking to use this software on a NASA
> facility and that is why we sent you the questions we did to comply with our
> security restrictions. If you could tell us where this software originated
> from that would be all we need to move forward. We have followed the link
> you suggested and could still not find this information.

Please read the very first page, https://cygwin.com/ , the two paragraphs at
the very top.

Cygwin itself, as a software product, is one library - cygwin1.dll.
And as is, it's rather useless for any applications.

Cygwin as an ecosystem is a collection of opensource software originating all
around the globe.


-- 
With best regards,
Andrey Repin
Wednesday, June 17, 2020 20:58:23

Sorry for my terrible english...


  parent reply	other threads:[~2020-06-17 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:59 Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-11 17:19 ` Brian Inglis
2020-06-17 15:37   ` [EXTERNAL] " Watson, Christian M. (GRC-V000)[Peerless Technologies Corp.]
2020-06-17 17:56     ` Bill Stewart
2020-06-17 18:04     ` Andrey Repin [this message]
2020-06-17 19:21     ` Marco Atzeri
2020-06-18  0:14       ` Brian Inglis
2020-06-18  0:44         ` [cygwin] " Jason Pyeron
2020-06-18  2:59           ` Brian Inglis
2020-06-18  3:17             ` Jason Pyeron
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=625906552.20200617210436@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=christian.m.watson@nasa.gov \
    --cc=cygwin@cygwin.com \
    /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).