From: Eli Zaretskii <eliz@is.elta.co.il>
To: Brian Youmans <3diff@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: new diff: gdb.texinfo
Date: Wed, 16 Jan 2002 23:38:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020117093701.13091E-100000@is> (raw)
In-Reply-To: <E16QyJL-0001JX-00@spider.gnu.org>
On Wed, 16 Jan 2002, Brian Youmans wrote:
> 1. I have removed the change I made adding the GFDL to the list of
> Invariant Sections in the copying permissions - RMS does not think it
> is proper to list it as an "Invariant Section", although it is
> effectively one anyways, since you can't alter or remove it.
Yes, the GFDL usage guidelines on www.gnu.org clearly say GFDL itself
shouldn't be marked invariant since its text already prohibits its
modifcation.
> 3. This makes more fixes to the multitables. Have I mentioned lately
> how much I *hate* multitables?
There's no reason to hate @multitable, IMHO, it's just that the GDB
manual abuses it: it tries to squeeze too much information into a
table, and the table items have too many @code markup in them, so TeX
cannot break the lines in a useful way. Unfortunately, I don't know
enough about the related subject matter (the remote protocol) to
rewrite that table.
> 4. I put in a FIXME at one spot I noticed where I think a word is
> missing.
Thanks, I will fix it.
Andrew, I don't know whether I should bother checking in these changes
on the branch anymore, what with your intent to release v5.2 from the
trunk. Please advise.
next prev parent reply other threads:[~2002-01-17 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 14:13 Brian Youmans
2002-01-16 23:38 ` Eli Zaretskii [this message]
2002-01-17 8:31 ` Andrew Cagney
2002-01-17 12:28 ` Eli Zaretskii
2002-01-20 3:49 ` Eli Zaretskii
2002-01-20 9:33 ` Andrew Cagney
2002-01-20 10:27 ` Eli Zaretskii
2002-01-17 2:59 ` Richard Earnshaw
2002-01-17 3:59 ` Eli Zaretskii
2002-01-17 7:21 ` Brian Youmans
2002-01-17 7:41 ` Richard Earnshaw
2002-01-20 3:48 ` Eli Zaretskii
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.1020117093701.13091E-100000@is \
--to=eliz@is.elta.co.il \
--cc=3diff@gnu.org \
--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