From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: GPL vs GFDL in generated files
Date: Wed, 18 Jun 2003 14:24:00 -0000 [thread overview]
Message-ID: <3EF07621.1000900@redhat.com> (raw)
In-Reply-To: <7263-Wed18Jun2003011744+0300-eliz@elta.co.il>
>> Date: Tue, 17 Jun 2003 17:08:02 -0400
>> From: Andrew Cagney <ac131313@redhat.com>
>>
>> ``I am not a lawyer''.
>
>
> Neither am I.
>
>
>> A longer term GDB plan is to use a common source for things like
>> gdbarch.[ch] (architecture vector source code) and gdbin.texinfo
>> (architecture vector documentation). GCC are now talking about doing
>> something similar. One issue that came up during their discussions was
>> the question of the GPL and GFDL being ``compatible'' - can a common
>> file be used to generate both.
>
>
> I would think that if only a part of the manual is produced from that
> common source, there should be no problem, but I'm not sure.
>
> How about asking RMS and/or the FSF lawyers?
GCC, who are looking at [d]oxygen(?), are ment to be doing this ->
deligate deligate deligate :-)
Andrew
prev parent reply other threads:[~2003-06-18 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 21:08 Andrew Cagney
2003-06-17 22:18 ` Eli Zaretskii
2003-06-18 14:24 ` Andrew Cagney [this message]
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=3EF07621.1000900@redhat.com \
--to=ac131313@redhat.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).