From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-78687-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 29181 invoked by alias); 25 Feb 2011 11:59:30 -0000
Received: (qmail 29173 invoked by uid 22791); 25 Feb 2011 11:59:30 -0000
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0	tests=AWL,BAYES_00,TW_WT,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 25 Feb 2011 11:59:24 +0000
Received: (qmail 7780 invoked from network); 25 Feb 2011 11:59:23 -0000
Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2)  by mail.codesourcery.com with ESMTPA; 25 Feb 2011 11:59:23 -0000
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 18/18] document the new VxWorks port
Date: Fri, 25 Feb 2011 12:01:00 -0000
User-Agent: KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.6.0; x86_64; ; )
Cc: Joel Brobecker <brobecker@adacore.com>, Jerome Guitton <guitton@adacore.com>, Eli Zaretskii <eliz@gnu.org>
References: <1298569763-18784-1-git-send-email-brobecker@adacore.com> <20110225114943.GB2254@adacore.com> <20110225115539.GG2495@adacore.com>
In-Reply-To: <20110225115539.GG2495@adacore.com>
MIME-Version: 1.0
Content-Type: Text/Plain;  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201102251159.21372.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-02/txt/msg00754.txt.bz2

On Friday 25 February 2011 11:55:39, Joel Brobecker wrote:
> > Not sure that it would make this much clearer, as "info tasks" exists
> > as well. An other source of confusion here is that "task" means
> > also something different in Ada.
> 
> But at the same time, we're saying threads when we really mean
> "VxWorks Tasks", no? I think that the "wtx" prefix in the command
> might help make things clearer.  Otherwise, how about "info wtx
> vxworks-tasks"?

Of put this under the "info os" mechanism?

-- 
Pedro Alves