From: Chaz <chaz@pokeit.co>
To: "cygwin-licensing@cygwin.com" <cygwin-licensing@cygwin.com>
Subject: Re: Bug in Cygwin Windows 8 group permissions
Date: Thu, 06 Dec 2012 12:50:00 -0000 [thread overview]
Message-ID: <00A2E1CD-0046-4E33-AD25-9513A0DEC4A8@pokeit.co> (raw)
In-Reply-To: <20121206080827.GA17192@calimero.vinschen.de>
On Dec 6, 2012, at 3:08 AM, Corinna Vinschen
> On Dec 6 01:19, Christopher Faylor wrote:
>> On Thu, Dec 06, 2012 at 12:43:50AM -0500, Chaz Littlejohn wrote:
>>> On Wed, Dec 5, 2012 at 4:26 AM, Corinna Vinschen wrote:
>>>> The most simple way to accomplish this is to add a sources download
>>>> URL where you provide the source packages of all the OSS packages you
>>>> use. It's not *that* much work.
>>>
>>> No problem, we'll add those links to the terms.
>>
>> Just to be really clear: These links should not be to the Cygwin web site.
>> You need to provide the exact sources that go with the binaries that you
>> distribute. You can't rely on the Cygwin site to provide those.
>
> Exactly. Apparently my wording was unclear. What I was trying to say
> is that you, Chaz, could create a sources download area on your web
> server where you provide the source packages of the OSS binaries you
> use. It's not sufficient to link to the upstream project page. That's
> a common misconception.
Ok, yes. That makes sense.Thanks for the clarification.
prev parent reply other threads:[~2012-12-06 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMgm8F0K9juGwfGy9DZ=DXMqWNkOk04fR_NUox+fGTwDW56Uug@mail.gmail.com>
[not found] ` <50BE8526.3030602@cygwin.com>
[not found] ` <CAMgm8F0f1uNyoeE-_SFSQCbOUcK-y9kj3saq0dBC3Rw4jxzL4w@mail.gmail.com>
2012-12-05 9:05 ` Chaz Littlejohn
2012-12-05 9:39 ` Corinna Vinschen
2012-12-06 6:14 ` Chaz Littlejohn
2012-12-06 6:21 ` Christopher Faylor
2012-12-06 8:26 ` Corinna Vinschen
2012-12-06 12:50 ` Chaz [this message]
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=00A2E1CD-0046-4E33-AD25-9513A0DEC4A8@pokeit.co \
--to=chaz@pokeit.co \
--cc=cygwin-licensing@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).