Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] License clarification for observer.texi
Date: Tue, 09 May 2006 20:29:00 -0000	[thread overview]
Message-ID: <u3bfj9c3b.fsf@gnu.org> (raw)
In-Reply-To: <20060509192721.GA13403@nevyn.them.org> (message from Daniel 	Jacobowitz on Tue, 9 May 2006 15:27:21 -0400)

> Date: Tue, 9 May 2006 15:27:21 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> I'm not sure what I need to ask the FSF now?

I suggest to ask whether it is okay to add to observers.texi the
simplified copyright blurb.  This is not a trivial question, since
observers.texi is covered by the GFDL license of the manual (see
below).

> I'd like to set the
> license on the file to one which is (A) acceptable to the FSF, (B)
> legally valid to include in the manual, and (C) legally valid to link
> with GDB - that's pretty unambiguous and I think we've found such a
> license.

Yes, we both agree that it is probably okay to make this change.
However, we are changing the distribution copyright of observers.texi
not only for the Debian distro, but for the FSF distro as well.  Since
the FSF is the copyright holder, I don't think we can change the
copyright without their consent, even if it's perfectly legal.

Btw, it may be that the current form of observers.texi is not legally
safe, either, since it currently has no copyright blurb at all.  By
contrast, the *.texi files that comprise the Emacs manual each have
the following text at their beginning:

    @c This is part of the Emacs manual.
    @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 1999, 2000,
    @c   2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
    @c See file emacs.texi for copying conditions.

and the full copyright is in emacs.texi.


  reply	other threads:[~2006-05-09 20:29 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
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 [this message]
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=u3bfj9c3b.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