From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22355 invoked by alias); 4 Jul 2011 20:02:06 -0000 Received: (qmail 22346 invoked by uid 22791); 4 Jul 2011 20:02:06 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 Jul 2011 20:01:53 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C73752BAB72; Mon, 4 Jul 2011 16:01:52 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cqGekd9bOJRk; Mon, 4 Jul 2011 16:01:52 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 72FE72BAB55; Mon, 4 Jul 2011 16:01:52 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 457D0145615; Mon, 4 Jul 2011 13:01:48 -0700 (PDT) Date: Mon, 04 Jul 2011 20:16:00 -0000 From: Joel Brobecker To: Thiago Jung Bauermann Cc: gdb-patches ml , Eli Zaretskii Subject: Re: [doc] Re: [RFC] s/preceed/precede/ Message-ID: <20110704200148.GT2407@adacore.com> References: <1309807927.4471.12.camel@hactar> <20110704194610.GR2407@adacore.com> <1309809372.4471.20.camel@hactar> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1309809372.4471.20.camel@hactar> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-07/txt/msg00124.txt.bz2 > Great. I forgot to mention that two of these typos are in error > messages. One related to the break-range command: > > - error (_("Invalid address range, end preceeds start.")); > + error (_("Invalid address range, end precedes start.")); > > and the other related to the find command: > > - error (_("Invalid search space, end preceeds start.")); > + error (_("Invalid search space, end precedes start.")); > > Does it matter? I guess not, since we only support parseable output in > the MI. I also think that it's better to fix this... -- Joel