From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: bug-gnulib <bug-gnulib@gnu.org>, emacs-devel@gnu.org
Subject: Re: Confusing license statements in some Gnulib imports
Date: Tue, 08 Feb 2011 21:51:58 -0800 [thread overview]
Message-ID: <4D522B7E.9000607@cs.ucla.edu> (raw)
In-Reply-To: <k262sucahe.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On 02/08/2011 04:33 PM, Glenn Morris wrote:
> In the Emacs trunk, eg arg-nonnull.h says:
>
> This program is free software: you can redistribute it and/or modify it
> under the terms of the GNU General Public License as published
> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> by the Free Software Foundation; [...]
> [...]
> See the GNU Lesser General Public License for more details.
> ^^^^^^
>
> This also seems to affect c++defs.h, warn-on-use.h, and lib/getopt_.h
> (at the _GL_ARG_NONNULL definition).
Thanks for reporting this. This seems to be a systematic problem in
gnulib, because gnulib-tool isn't smart enough (and arguably should
not be smart enough) to rewrite license names that cross line boundaries.
For example, arg-nonnull.h's original source says this:
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
and the newline between the "GNU" and the "Lesser" causes gnulib-tool
to miss that instance of "GNU Lesser General Public License".
I looked for every instance of this I could find in gnulib, and
came up with the attached patch. It's mostly mechanical and
it is so large (540 kB) that I compressed it. I haven't installed
this into gnulib yet since I'd like another pair of eyes to
look at it.
[-- Attachment #2: patch.txt.gz --]
[-- Type: application/x-gzip, Size: 32159 bytes --]
next prev parent reply other threads:[~2011-02-09 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:33 Confusing license statements in some Gnulib imports Glenn Morris
2011-02-09 5:51 ` Paul Eggert [this message]
2011-02-09 11:22 ` Bruno Haible
2011-02-09 17:46 ` Paul Eggert
2011-02-09 19:59 ` Bruno Haible
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=4D522B7E.9000607@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.