From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: joseph@codesourcery.com, stan@codesourcery.com, gdb@sourceware.org
Subject: Re: Autogenerate gdbarch doc for internals manual
Date: Fri, 01 Aug 2008 18:38:00 -0000 [thread overview]
Message-ID: <ufxpomvik.fsf@gnu.org> (raw)
In-Reply-To: <48934A42.7060307@codesourcery.com>
> Date: Fri, 01 Aug 2008 10:39:14 -0700
> From: Stan Shebs <stan@codesourcery.com>
> CC: Stan Shebs <stan@codesourcery.com>, gdb@sourceware.org
>
> how does that work for libiberty, which collects snippets from LGPL
> files and pastes them into functions.texi, which is included in the
> GFDLed manual?
Not only libiberty does that; bfd does that as well. I very much
doubt that this is somehow an omission on the part of FSF lawyers.
next prev parent reply other threads:[~2008-08-01 18:38 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 [this message]
2008-08-01 18:50 ` Daniel Jacobowitz
2008-08-01 18:35 ` Eli Zaretskii
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=ufxpomvik.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