From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13827 invoked by alias); 17 Jan 2002 07:38:13 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13793 invoked from network); 17 Jan 2002 07:38:12 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 17 Jan 2002 07:38:12 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id JAA13168; Thu, 17 Jan 2002 09:37:28 +0200 (IST) Date: Wed, 16 Jan 2002 23:38:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Brian Youmans <3diff@gnu.org> cc: gdb-patches@sources.redhat.com Subject: Re: new diff: gdb.texinfo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-01/txt/msg00475.txt.bz2 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.