Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: stan@codesourcery.com, gdb@sourceware.org
Subject: Re: Autogenerate gdbarch doc for internals manual
Date: Fri, 01 Aug 2008 18:35:00 -0000	[thread overview]
Message-ID: <uhca4mvm3.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0808011719410.3945@digraph.polyomino.org.uk>

> Date: Fri, 1 Aug 2008 17:22:12 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb@sourceware.org
> 
> You have the issue that's been discussed before in the GCC context: the 
> need for an appropriate license text on gdbarch.sh to allow parts of it to 
> be used in the manual that's under a different license from the code.  

That depends on how Stan writes those parts.  We could, for instance,
have some template outside gdbarch.sh which the script will edit to
produce the actual Texinfo.

In general, there's any number of ways to do this job without
violating the GNU licenses.

> Good luck getting the FSF to produce a GPLv3 exception text for this in 
> reasonable time given how long all the other exceptions have taken so far 

RMS always asserted that such jobs will not present any
license-related problems in practice.  I can run the idea through him
in advance and see if he has any specific advice, if Stan would like
that before he embarks on doing this job.


  parent reply	other threads:[~2008-08-01 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 17:06 Stan Shebs
2008-08-01 17:22 ` Joseph S. Myers
2008-08-01 17:39   ` Stan Shebs
2008-08-01 17:51     ` Mark Kettenis
2008-08-01 18:38     ` Eli Zaretskii
2008-08-01 18:50       ` Daniel Jacobowitz
2008-08-01 18:35   ` Eli Zaretskii [this message]
2008-08-01 18:55     ` Stan Shebs
2008-08-01 18:32 ` Eli Zaretskii
2008-08-01 18:34 ` Jeremy Bennett

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=uhca4mvm3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=stan@codesourcery.com \
    /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