public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: cygwin@cygwin.com
Subject: Re: Commercial use of cygwin
Date: Sat, 14 Nov 2020 08:50:24 +0100	[thread overview]
Message-ID: <3ff604bf-5016-2f62-bea0-8fd97c3bad0c@gmail.com> (raw)
In-Reply-To: <5FAF85CB.8000705@tlinx.org>

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



  reply	other threads:[~2020-11-14  7:50 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 [this message]
2020-12-12 17:27       ` Hamish McIntyre-Bhatty
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=3ff604bf-5016-2f62-bea0-8fd97c3bad0c@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.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).