public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin-OpenSSH 8.2.2.2
Date: Tue, 24 Mar 2020 10:23:21 +0000	[thread overview]
Message-ID: <CA+kUOakKrvkFGDSHjPW8omZQfiykzCbqjQzMvN0gJsQ_xHb6cg@mail.gmail.com> (raw)
In-Reply-To: <5E795C94.5070306@tlinx.org>

On Tue, 24 Mar 2020 at 01:04, L A Walsh wrote:
>
> On 2020/02/27 14:30, Brian Inglis wrote:
> > No, you must backport all sources to the current and all previous versions
> ----
>     What all previous versions?  Going back to year 2000 or before?
>
> That sounds a bit onerous.

I think the point Brian was trying to make was that it is not
sufficient to provide the source code in future releases of Bill's
Cygwin-OpenSSH package. To comply with the GPL requirements, Bill
would need to make available all the relevant source code for every
binary release he has made of his package.

Alternatively: yes. The GPL _is_ onerous. That's sort of the point: it
forces people to make source code available even when they don't want
to, regardless of whether that's because they don't want others
changing their code or because they just don't want to do the
additional work.

  reply	other threads:[~2020-03-24 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 21:02 [ANN] " Bill Stewart
2020-02-27  6:47 ` ASSI
2020-02-27 14:51   ` Bill Stewart
2020-02-27 18:22     ` Henry S. Thompson
2020-02-27 18:52     ` Achim Gratz
2020-02-27 19:37       ` Bill Stewart
2020-02-27 22:31         ` Brian Inglis
2020-02-28 14:51           ` Bill Stewart
2020-02-28 17:45             ` Andrew Schulman via cygwin
2020-02-28 21:20             ` Andrey Repin
2020-03-01 11:53             ` Achim Gratz
2020-03-24  1:04           ` L A Walsh
2020-03-24 10:23             ` Adam Dinwoodie [this message]
2020-03-24 15:07               ` Bill Stewart

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=CA+kUOakKrvkFGDSHjPW8omZQfiykzCbqjQzMvN0gJsQ_xHb6cg@mail.gmail.com \
    --to=adam@dinwoodie.org \
    --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).