From: "Bishmer J. Sekaran" <bishmer@scorpionrock.com>
To: mhw@netris.org
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Add dcfldd
Date: Tue, 12 Aug 2014 23:07:56 +0800 [thread overview]
Message-ID: <53EA2DCC.9020304@scorpionrock.com> (raw)
Mark,
Thanks for comments on technical points. I'll fix the mirror link and
re-mail the patch with mutt.
> Is the license really gpl2 and not gpl2+?
re: Licensing, my impression was that "gpl2+" only applies if the
authors specifically invoke "any later version" when they distribute the
software, per clause 9 of the GPL 2
"9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Program does not specify a version
number of this License, you may choose any version ever published by the
Free Software Foundation."
Upstream lists the project as:
"License
GNU General Public License version 2.0 (GPLv2)"
http://sourceforge.net/projects/dcfldd/
Am I in error?
-Bishmer
next reply other threads:[~2014-08-12 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 15:07 Bishmer J. Sekaran [this message]
2014-08-12 15:22 ` [PATCH] Add dcfldd Eric Bavier
2014-08-13 3:34 ` mhw
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 15:00 Bishmer J. Sekaran
2014-08-12 18:27 ` Ludovic Courtès
2014-08-04 3:25 Bishmer J. Sekaran
2014-08-04 12:00 ` Bishmer J. Sekaran
2014-08-06 17:17 ` Andreas Enge
2014-08-11 5:36 ` Mark H Weaver
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=53EA2DCC.9020304@scorpionrock.com \
--to=bishmer@scorpionrock.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.