From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20384 invoked by alias); 10 Apr 2002 16:30:46 -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 20376 invoked from network); 10 Apr 2002 16:30:44 -0000 Received: from unknown (HELO pasiphae01.frii.com) (216.17.128.33) by sources.redhat.com with SMTP; 10 Apr 2002 16:30:44 -0000 Received: from deimos.frii.net (deimos.frii.com [216.17.128.2]) by pasiphae01.frii.com (8.12.2/8.12.2) with ESMTP id g3AGUfAn036048 for ; Wed, 10 Apr 2002 10:30:41 -0600 (MDT) Received: from ari-co8-245.rasserver.net (ari-co8-245.rasserver.net [204.32.206.245]) by deimos.frii.net (8.12.2/8.12.2) with ESMTP id g3AGUPbl097226 for ; Wed, 10 Apr 2002 10:30:34 -0600 (MDT) Date: Wed, 10 Apr 2002 09:30:00 -0000 From: "Theodore A. Roth" X-X-Sender: troth@bozoland.mynet To: gdb-patches@sources.redhat.com Subject: typos in gdbint.texinfo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00400.txt.bz2 Found these while skimming through gdbint.info. Ted Roth * gdbint.texinfo (Releasing GDB): Fix some typos. Index: gdb/doc/gdbint.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v retrieving revision 1.72 diff -u -p -r1.72 gdbint.texinfo --- gdb/doc/gdbint.texinfo 6 Apr 2002 00:02:52 -0000 1.72 +++ gdb/doc/gdbint.texinfo 10 Apr 2002 16:12:42 -0000 @@ -4628,7 +4628,7 @@ symbol to write conditional code which s such hosts. @findex IS_DIR_SEPARATOR -@item IS_DIR_SEPARATOR (@var{c} +@item IS_DIR_SEPARATOR (@var{c}) Evaluates to a non-zero value if @var{c} is a directory separator character. On Unix and GNU/Linux systems, only a slash @file{/} is such a character, but on Windows, both @file{/} and @file{\} will @@ -4930,7 +4930,7 @@ The @file{gdb/MAINTAINERS} file still ho @item Don't fix something on the branch unless/until it is also fixed in the trunk. If this isn't possible, mentioning it in the @file{gdb/PROBLEMS} -file is better than committing a hack +file is better than committing a hack. @item When considering a patch for the branch, suggested criteria include: Does it fix a build? Does it fix the sequence @kbd{break main; run} @@ -4953,8 +4953,8 @@ reason) support for a new host are consi @section Obsolete any code Before anything else, poke the other developers (and around the source -code) to see there is anything that can be removed from @value{GDBN} (an -old target, an unused file). +code) to see if there is anything that can be removed from @value{GDBN} +(an old target, an unused file). Obsolete code is identified by adding an @code{OBSOLETE} prefix to every line. Doing this means that it is easy to identify obsolete code when