From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Commercial use of cygwin
Date: Sat, 12 Dec 2020 17:27:16 +0000 [thread overview]
Message-ID: <DB7PR02MB399642C9DCA3E3463C5F2A97E7C90@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <3ff604bf-5016-2f62-bea0-8fd97c3bad0c@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1698 bytes --]
On 14/11/2020 07:50, Marco Atzeri via Cygwin wrote:
> On 14.11.2020 08:22, L A Walsh wrote:
>> On 2020/11/12 02:42, Marco Atzeri via Cygwin copied the whole note:
>>> On 12.11.2020 09:42, Antonio Sidoti via Cygwin wrote:
>>> I was looking into using Cygwin for commercial use...
>> [27 lines of duplicate text]
>>>
>>> in general there is no restriction on usage.
>>> Marco
>> If you are going to bottom post, please trim your quotes.
>> If you need to quote the original for context, only quote
>> what is needed for context. In a threaded
>> reader, your reply is placed under the original poster's
>> email, where, if a reader is interested, it was just read.
>> Duplicating the entire note isn't necessary nor, I'd bet,
>> really wanted, by most.
>>
>
> Hi Linda,
> usually I agree, but he put down a specific list of DLL's
> and I replied with a specific list of License.
>
> 27 lines are not a lot, in my experience.
> There were much worst example than my mail to complain
> about on this mailing list.
>
> Cheers
> Marco
Do the points made here also apply to commercial but open-source use of
Cygwin?
For extra context, I have an application with bundles parts of Cygwin
and libraries built against Cygwin. None of the source or binaries is
modified.
I know I at least have to state which packages are included in the
bundle and provide links to the source for those, but I am not sure if
it is required that I eg provide a downloadable compressed folder with
complete source for everything.
Can anyone give me some advice? The work everyone does for Cygwin is
valuable and I certainly don't intend to claim any of it is mine.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-12 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 8:42 Antonio Sidoti
2020-11-12 10:42 ` Marco Atzeri
2020-11-14 7:22 ` L A Walsh
2020-11-14 7:50 ` Marco Atzeri
2020-12-12 17:27 ` Hamish McIntyre-Bhatty [this message]
2020-12-12 18:44 ` Adam Dinwoodie
2020-12-13 16:43 ` Hamish McIntyre-Bhatty
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=DB7PR02MB399642C9DCA3E3463C5F2A97E7C90@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).