From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Mon, 12 Oct 2009 18:26:00 -0000 [thread overview]
Message-ID: <m3vdiktqmx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091012182011.GA9395@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Mon, 12 Oct 2009 20:20:11 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> On Mon, 12 Oct 2009 20:13:38 +0200, Daniel Jacobowitz wrote:
>> Sure you can. But the comment would be under the GPL. The resulting
>> manual (the GDB Internals manual, not the gdbint.texinfo source file)
>> could not be distributed under the GFDL.
Jan> I expected to start some new separate GDB Reference Manual with whatever
Jan> compliant license (therefore probably the GPLv3 one).
I imagine that the FSF would require us to GFDL any new manual.
I support this effort in general but it can't really be resolved here.
Jan> The new file format (such as gtk-doc output choices) would be difficult to
Jan> merge with existing gdbint texinfo source or its output formats.
I am purposely avoiding this discussion until the legal stuff is dealt
with :-)
Tom
next prev parent reply other threads:[~2009-10-12 18:26 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 [this message]
2009-10-12 18:30 ` Jan Kratochvil
2009-10-12 18:54 ` Eli Zaretskii
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=m3vdiktqmx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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