zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: Kete <kete@ninthfloor.org>
Cc: zsh-workers@zsh.org
Subject: Re: Minor License bug
Date: Sun, 5 Jan 2014 00:50:03 +0100	[thread overview]
Message-ID: <20140104235002.GD27889@sym.noone.org> (raw)
In-Reply-To: <3082437.VD4yfJVIvD@knossos>

Hi Kete,

On Sat, Jan 04, 2014 at 11:58:51AM -0500, Kete wrote:
> This is a minor bug report. In the license, 
> http://sourceforge.net/p/zsh/code/ci/master/tree/LICENCE, the GPL should be 
> the General Public License, not GNU Public License. It's also the GNU GPL or 
> GNU General Public License: http://www.gnu.org/licenses/gpl.html.

This is indeed a bug, thanks for reporting it.

I've verified that there's no other occurrence of this issue in the
current git checkout.

Here's a patch to fix this issue:

>From 913bf9278b257dbf144db1e80dd3fac354794b56 Mon Sep 17 00:00:00 2001
From: Axel Beckert <abe@deuxchevaux.org>
Date: Sun, 5 Jan 2014 00:42:13 +0100
Subject: [PATCH] Fix GPL name in LICENCE

---
 LICENCE | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/LICENCE b/LICENCE
index 6be3a8a..1fb1fc4 100644
--- a/LICENCE
+++ b/LICENCE
@@ -2,11 +2,11 @@ Unless otherwise noted in the header of specific files, files in this
 distribution have the licence shown below.
 
 However, note that certain shell functions are licensed under versions
-of the GNU Public Licence.  Anyone distributing the shell as a binary
-including those files needs to take account of this.  Search shell
-functions for "Copyright" for specific copyright information.
-None of the core functions are affected by this, so those files
-may simply be omitted.
+of the GNU General Public Licence.  Anyone distributing the shell as a
+binary including those files needs to take account of this.  Search
+shell functions for "Copyright" for specific copyright information.
+None of the core functions are affected by this, so those files may
+simply be omitted.
 
 --

I had to rewrap that paragraph. For reference here's the according
wdiff:

However, note that certain shell functions are licensed under versions
of the GNU {+General+} Public Licence.  Anyone distributing the shell as a
binary including those files needs to take account of this.  Search
shell functions for "Copyright" for specific copyright information.
None of the core functions are affected by this, so those files may
simply be omitted.

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | abe@deuxchevaux.org  (Mail)
 X   See http://www.asciiribbon.org/              | abe@noone.org (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)


      reply	other threads:[~2014-01-04 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 16:58 Kete
2014-01-04 23:50 ` Axel Beckert [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=20140104235002.GD27889@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=kete@ninthfloor.org \
    --cc=zsh-workers@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).