From: Brian Youmans <3diff@gnu.org>
To: eliz@is.elta.co.il
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: More (C) tweeks for printed manual
Date: Tue, 15 Jan 2002 07:27:00 -0000 [thread overview]
Message-ID: <E16QVUk-0002oy-00@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020115094815.23380N-100000@is> (message from Eli Zaretskii on Tue, 15 Jan 2002 09:49:13 +0200 (IST))
Maybe RMS just forgot to ask about including the FDL? It does need to
be included. Just like when you give someone a copy of the source code
you need to include a copy of the GPL, when you give someone a copy of
the manual you need to include a copy of the FDL.
(That is why we are not asking people to use the FDL for very short pieces
of documentation - it would be silly to add a 6 or 8 page license to a
very short piece of doc.)
The copy of gdbmi.texinfo I looked at was the one in the 5.1.0.1 distribution.
Maybe someone corrected the problem I saw with the "Invariant Sections" already?
- Brian Youmans, FSF office staff
next prev parent reply other threads:[~2002-01-15 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 20:09 Andrew Cagney
2002-01-14 23:50 ` Eli Zaretskii
2002-01-15 7:27 ` Brian Youmans [this message]
2002-01-15 8:07 ` Andrew Cagney
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=E16QVUk-0002oy-00@fencepost.gnu.org \
--to=3diff@gnu.org \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@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