From: L A Walsh <cygwin@tlinx.org>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Commercial use of cygwin
Date: Fri, 13 Nov 2020 23:22:51 -0800 [thread overview]
Message-ID: <5FAF85CB.8000705@tlinx.org> (raw)
In-Reply-To: <34a5e2b9-5179-c0b6-e8b0-1245e7a4578f@gmail.com>
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.
next prev parent reply other threads:[~2020-11-14 7:23 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 [this message]
2020-11-14 7:50 ` Marco Atzeri
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=5FAF85CB.8000705@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=marco.atzeri@gmail.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).