From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] License clarification for observer.texi
Date: Mon, 08 May 2006 21:24:00 -0000 [thread overview]
Message-ID: <uody89puv.fsf@gnu.org> (raw)
In-Reply-To: <20060508210440.GA18323@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 8 May 2006 17:04:40 -0400)
> Date: Mon, 8 May 2006 17:04:40 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> The file is included directly into the manual, so must be covered by the
> GFDL. But the header file generated from it by observer.sh (gdb/observer.h
> in the build tree) has a GPL notice added. The GFDL and GPL are not
> compatible to this degree. Even the FSF agrees about this - the
> FDL suggests releasing code fragments under the GPL in parallel to including
> them in the manual.
>
> So, this patch marks observer.texi as distributable under both licenses.
Perhaps I'm missing something, but I don't see any need to do this.
observer.sh already puts a GPL blurb into observer.h, so why would we
need to add GPL to observer.texi? There's no real code in the
portions extracted to observer.h to justify any level of bother, IMO.
What were the problems raised on debian-legal, and did they consult
the FSF?
> Does anyone disapprove of this change? Or, feel sufficiently concerned by
> it that you would prefer I contact the FSF to confirm? I don't feel that it
> is necessary, since I am dealing strictly with the FSF's preferred licenses
> for code and for manuals, and strictly for manual already used as code.
If the two licenses are incompatible, how do we know we can distribute
a file under both of them?
next prev parent reply other threads:[~2006-05-08 21:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 21:04 Daniel Jacobowitz
2006-05-08 21:24 ` Eli Zaretskii [this message]
2006-05-08 22:18 ` Daniel Jacobowitz
2006-05-09 3:32 ` Eli Zaretskii
2006-05-09 4:06 ` Daniel Jacobowitz
2006-05-09 18:57 ` Eli Zaretskii
2006-05-09 19:03 ` Daniel Jacobowitz
2006-05-09 19:29 ` Eli Zaretskii
2006-05-09 19:35 ` Daniel Jacobowitz
2006-05-09 12:59 ` Daniel Jacobowitz
2006-05-09 19:20 ` Eli Zaretskii
2006-05-09 19:27 ` Daniel Jacobowitz
2006-05-09 20:29 ` Eli Zaretskii
2006-05-09 20:34 ` Daniel Jacobowitz
2006-05-10 3:23 ` Eli Zaretskii
2006-05-10 3:52 ` Daniel Jacobowitz
2006-05-10 17:43 ` Eli Zaretskii
2006-05-09 20:50 ` Daniel Jacobowitz
2006-05-10 14:59 ` Daniel Jacobowitz
2006-05-10 18:10 ` Eli Zaretskii
2006-05-10 18:49 ` Daniel Jacobowitz
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=uody89puv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox