From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2802 invoked by alias); 25 Feb 2011 12:15:42 -0000 Received: (qmail 2791 invoked by uid 22791); 25 Feb 2011 12:15:40 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_WT 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; Fri, 25 Feb 2011 12:15:36 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D1EAC2BAEA2; Fri, 25 Feb 2011 07:15:34 -0500 (EST) 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 1jxshhckukpi; Fri, 25 Feb 2011 07:15:34 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 57F442BAE86; Fri, 25 Feb 2011 07:15:34 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 24323145A56; Fri, 25 Feb 2011 16:15:27 +0400 (RET) Date: Fri, 25 Feb 2011 12:56:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: Jerome Guitton , gdb-patches@sourceware.org Subject: Re: [PATCH 18/18] document the new VxWorks port Message-ID: <20110225121527.GH2495@adacore.com> References: <838vx5rzf8.fsf@gnu.org> <20110225102624.GB3211@adacore.com> <83ipw8qsfe.fsf@gnu.org> <20110225112647.GA2254@adacore.com> <83d3mgqr7y.fsf@gnu.org> <20110225114413.GF2495@adacore.com> <20110225114943.GB2254@adacore.com> <20110225115539.GG2495@adacore.com> <20110225120115.GC2254@adacore.com> <8362s8qpum.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8362s8qpum.fsf@gnu.org> 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-02/txt/msg00758.txt.bz2 > > Interesting name. This command used to be called "info vxworks-tasks" :) > > Well, it sounds like a good name to me ;-) OK, so it sounds like we are converging (I read your other message, and it seemed to me that we were saying the same thing). We originally renamed that command because we didn't want to pollute the "info" prefix with VxWorks-specific commands - which is why we created the "info wtx" sub-prefix. So would "info wtx vxworks-tasks" be OK? -- Joel