From: Michal Ludvig <mludvig@suse.cz>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: kettenis@chello.nl, gdb-patches@sources.redhat.com
Subject: Re: [RFA/i386newframe] info cfi command
Date: Thu, 29 May 2003 14:56:00 -0000 [thread overview]
Message-ID: <3ED61F95.7090608@suse.cz> (raw)
In-Reply-To: <8011-Thu29May2003171558+0300-eliz@elta.co.il>
Eli Zaretskii told me that:
> If the code is approved (I cannot approve it), please write a change
> for the manual that documents the new command. I'd like to avoid a
> situation where we have undocumented commands.
To which section should it go? Examining Data? Source and machine code?
Information about a frame? Somewhere else?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
next prev parent reply other threads:[~2003-05-29 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 13:46 Michal Ludvig
2003-05-29 14:16 ` Eli Zaretskii
2003-05-29 14:56 ` Michal Ludvig [this message]
2003-05-29 16:29 ` Mark Kettenis
2003-05-29 18:14 ` Andrew Cagney
2003-05-30 12:33 ` Michal Ludvig
2003-05-31 16:35 ` Mark Kettenis
2003-05-31 16:47 ` Andrew Cagney
2003-05-31 16:49 ` Michal Ludvig
2003-06-01 16:24 ` Eli Zaretskii
2003-06-03 0:39 ` Michael Snyder
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=3ED61F95.7090608@suse.cz \
--to=mludvig@suse.cz \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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