From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5087 invoked by alias); 28 Dec 2011 03:43:43 -0000 Received: (qmail 5078 invoked by uid 22791); 28 Dec 2011 03:43:42 -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; Wed, 28 Dec 2011 03:43:29 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id D806B2BB28B; Tue, 27 Dec 2011 22:43:28 -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 mWU8T5ze9N9y; Tue, 27 Dec 2011 22:43:28 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 5C2CC2BB10E; Tue, 27 Dec 2011 22:43:28 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 2E628145615; Tue, 27 Dec 2011 19:43:17 -0800 (PST) Date: Wed, 28 Dec 2011 03:51:00 -0000 From: Joel Brobecker To: Stan Shebs Cc: Eli Zaretskii , gdb-patches@sourceware.org Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4) Message-ID: <20111228034317.GJ23376@adacore.com> References: <4E95DC58.7030805@codesourcery.com> <4ECD3496.1070609@codesourcery.com> <4EF9497B.9020501@earthlink.net> <4EFA54FF.1080307@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EFA54FF.1080307@earthlink.net> 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-12/txt/msg00860.txt.bz2 > For my part, I would tend to favor "info os" for those kinds of data > that are generic enough to be found on more than one target OS. > Things like processes, semaphores, and sockets are found across a > broad range of systems large and small, and it seems unduly pedantic > to require users to do "info linux semaphores" when targeting Linux, > but "info bsd sem" for BSD - or worse, "info freebsd sem" vs "info > openbsd sem" - and which flavor of BSD is Darwin most like, again? > :-) Putting things under "info os" means less detail for users to > remember. I tend to agree with that. Otherwise, we end up with exactly what you explained, inconsistent interface across platforms. The discussion we are having is also an indicator that we should not put this in the 7.4 branch as well, I am afraid. -- Joel