From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
Date: Wed, 28 Dec 2011 03:51:00 -0000 [thread overview]
Message-ID: <20111228034317.GJ23376@adacore.com> (raw)
In-Reply-To: <4EFA54FF.1080307@earthlink.net>
> 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
next prev parent reply other threads:[~2011-12-28 3:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:29 [PATCH] Add extra 'info os' information types for Linux Kwok Cheung Yeung
2011-10-21 23:38 ` Tom Tromey
2011-11-23 18:00 ` Kwok Cheung Yeung
2011-12-27 4:56 ` [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4) Stan Shebs
2011-12-27 9:32 ` Eli Zaretskii
2011-12-27 21:30 ` Mark Kettenis
2011-12-27 23:23 ` Eli Zaretskii
2011-12-28 20:48 ` Mark Kettenis
2011-12-28 0:05 ` Stan Shebs
2011-12-28 3:51 ` Joel Brobecker [this message]
2011-12-28 6:02 ` Eli Zaretskii
2012-01-02 12:08 ` Pedro Alves
2012-01-02 12:35 ` Eli Zaretskii
2012-01-02 19:31 ` Pedro Alves
2012-01-03 3:05 ` Joel Brobecker
2012-01-02 18:15 ` Doug Evans
2012-01-02 19:19 ` Pedro Alves
2012-01-02 19:41 ` Tom Tromey
2011-12-29 20:34 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111228034317.GJ23376@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox