Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Mon, 12 Oct 2009 18:54:00 -0000	[thread overview]
Message-ID: <83ws30igr5.fsf@gnu.org> (raw)
In-Reply-To: <m3zl7wwn7q.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb@sourceware.org
> Date: Mon, 12 Oct 2009 11:12:25 -0600
> 
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> May the GDB project start using some tool to format documentation
> Jan> from the sources?  One could move the appropriate parts of
> Jan> gdb/doc/gdbint.texinfo into gdb/*.c along the patches being
> Jan> submitted, keeping in gdb/doc/gdbint.texinfo only the abstract
> Jan> parts in the future.
> 
> I would like to do this, but my understanding is that there is a
> licensing problem, in that the source is GPL and the documentation is
> GFDL.  (Joseph Myers has mentioned this several times on the GCC lists.)

Then how come libiberty and other packages do that?

I'd suggest to clear this up with RMS.

> Apparently we got some kind of special permission for observer.texi, so
> I suppose it is possible in principle.

observer.texi is not documentation, it's code written in Texinfo.


  parent reply	other threads:[~2009-10-12 18:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 16:14 Jan Kratochvil
2009-10-12 17:12 ` Tom Tromey
2009-10-12 17:16   ` Jan Kratochvil
2009-10-12 18:00     ` Daniel Jacobowitz
2009-10-12 18:07       ` Jan Kratochvil
2009-10-12 18:13         ` Daniel Jacobowitz
2009-10-12 18:20           ` Jan Kratochvil
2009-10-12 18:26             ` Tom Tromey
2009-10-12 18:30               ` Jan Kratochvil
2009-10-12 18:54   ` Eli Zaretskii [this message]
2009-10-12 19:10     ` Daniel Jacobowitz
2009-10-12 19:25     ` Tom Tromey
2009-10-12 20:23       ` Eli Zaretskii
2009-10-12 18:57 ` Eli Zaretskii
2009-10-13  8:23   ` Jeremy Bennett
2009-10-13 18:16     ` Eli Zaretskii
2009-10-13 19:13       ` Jan Kratochvil
2009-10-13 19:18         ` Eli Zaretskii
2009-10-27 10:07 ` Mark Kettenis

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=83ws30igr5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tromey@redhat.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