From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] New command "info proc" for Linux
Date: Wed, 16 Jan 2002 09:13:00 -0000 [thread overview]
Message-ID: <3C45B35B.653A@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020116080549.2698F-100000@is>
Eli Zaretskii wrote:
>
> On Tue, 15 Jan 2002, Michael Snyder wrote:
>
> > Committed.
>
> 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.
next prev parent reply other threads:[~2002-01-16 17:13 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 [this message]
2002-01-16 9:26 ` Eli Zaretskii
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=3C45B35B.653A@redhat.com \
--to=msnyder@redhat.com \
--cc=drow@mvista.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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