From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com, Brian Youmans <3diff@gnu.org>
Subject: Re: More (C) tweeks for printed manual
Date: Mon, 14 Jan 2002 23:50:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020115094815.23380N-100000@is> (raw)
In-Reply-To: <3C43AB4C.9000904@cygnus.com>
On Mon, 14 Jan 2002, Andrew Cagney wrote:
> Brian Y has found some more (C) related tweeks related to the manual.
> The FSF are getting ready for another print run so are going over things
> with a fine tooth comb.
Sorry, I don't understand: why is the GFDL text added to the manual?
Richard Stallman never asked for that, IIRC. Not every manual comes with
a copy of GFDL, and neither is there AFAIK a requirement that they do.
All of the other changes are because of this inclusion; there's
nothing wrong with the copyright notices or the years mentioned there
right now.
Brian, could you please explain the reason for the change?
next prev parent reply other threads:[~2002-01-15 7:50 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 [this message]
2002-01-15 7:27 ` Brian Youmans
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=Pine.SUN.3.91.1020115094815.23380N-100000@is \
--to=eliz@is.elta.co.il \
--cc=3diff@gnu.org \
--cc=ac131313@cygnus.com \
--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