unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: Add microcom
Date: Tue, 13 Sep 2016 13:50:13 -0400	[thread overview]
Message-ID: <20160913175013.GA32237@jasmine> (raw)
In-Reply-To: <20160913173749.GA25835@jocasta.intra>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Tue, Sep 13, 2016 at 07:37:49PM +0200, John Darrington wrote:
> On Tue, Sep 13, 2016 at 11:36:17AM -0400, Leo Famulari wrote:
>      On Sun, Sep 11, 2016 at 06:56:58PM +0200, John Darrington wrote:
>      > +    (license gpl2+)))
>      
>      My interpretation of the first paragraph of COPYING [0] is that the
>      package is licensed under the GPL version 2 only. What do you think?
> 
> All the .c files in the package explicitly say "either version 2 of the License,
>  or (at your option) any later version".

Okay, I guess the statement in COPYING [0] can be interpreted to not
exclude distribution under later versions. It merely confirms that you
can distribute under version 2.

[0]
All files included in microcom are distributable under the "GNU GENERAL
PUBLIC LICENSE version 2". (Some might have the "or any later version"
phrase; this doesn't affect the previous statement though.) If the file
doesn't specify a license explicitly, assume "version 2 only". The "GNU
GENERAL PUBLIC LICENSE version 2" is appended below.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-09-13 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 16:56 [PATCH] gnu: Add microcom John Darrington
2016-09-13 15:36 ` Leo Famulari
2016-09-13 17:37   ` John Darrington
2016-09-13 17:50     ` Leo Famulari [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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160913175013.GA32237@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=jmd@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).