From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: msnyder@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] New command "info proc" for Linux
Date: Wed, 16 Jan 2002 09:26:00 -0000 [thread overview]
Message-ID: <8011-Wed16Jan2002192316+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C45B35B.653A@redhat.com> (message from Michael Snyder on Wed, 16 Jan 2002 09:07:39 -0800)
> Date: Wed, 16 Jan 2002 09:07:39 -0800
> From: Michael Snyder <msnyder@redhat.com>
> >
> > Michael, please don't forget the documentation. Thanks.
>
> Not straightforward. Couple of issues:
>
> 1) The old implementation of the "info proc" command was
> poorly documented -- many of the documented sub-commands
> were never implemented. And the command was only available
> on "/proc" systems (real ones, not Linux).
>
> 2) The stuff I've just added will ONLY work on Linux,
> not on other ("real") /proc systems.
Does that mean the functionality of this command differs on these two
classes of systems? If so, we could:
(a) document the functionality on both classes, telling which parts
work on what systems;
or
(b) document the GNU/Linux functionality that you just added, and
leave the docs of what the command does on ``real'' /proc systems as
it is now.
The latter will probably be easier for you (no need to figure out code
written by someone else ;-), and it doesn't make the situation worse
than it is now. So I won't object if you do only (b). (If you do, it
is possible that the Linux-specific docs could go into a new
subsection of the "Native" node, where system-specific features are
described.
Does that address your concerns?
next prev parent reply other threads:[~2002-01-16 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 12:14 Michael Snyder
2002-01-11 16:25 ` Daniel Jacobowitz
2002-01-15 12:11 ` Michael Snyder
2002-01-15 22:07 ` Eli Zaretskii
2002-01-16 9:13 ` Michael Snyder
2002-01-16 9:26 ` Eli Zaretskii [this message]
2002-01-16 9:52 ` Michael Snyder
2002-01-16 11:19 ` Eli Zaretskii
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=8011-Wed16Jan2002192316+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.com \
/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