From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: info macro [-at LOCATION,]
Date: Tue, 11 Nov 2014 15:41:00 -0000 [thread overview]
Message-ID: <83lhnhn3se.fsf@gnu.org> (raw)
In-Reply-To: <7612.1415714475@usendtaylorx2l>
> cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Tue, 11 Nov 2014 09:01:15 -0500
> From: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
>
> > Thanks. I think this warrants a NEWS entry as well.
>
> Thanks. How are diffs for NEWS handled?
Like any other file you modify.
> For the text, how about:
>
> * New options
>
> The info macro command now takes an optional location ([-at LOCATION,])
> for determining which definition, if any, of the macro is in scope. If
> left unspecified it, as before, uses the source and line associated with
> the current program counter.
Fine with me, thanks.
> > > * gdb.texinfo: Document new -at LOCATION option of the 'info
> > > macro' command.
> >
> > Please state the node in which the change was made (as if it were a
> > function, i.e. in parentheses).
>
> Okay, how about:
>
> 2014-11-10 David Taylor <dtaylor@emc.com>
>
> * gdb.texinfo (Macros): Document new -at LOCATION option of
> the 'info macro' command.
OK.
> > And second, "it is used instead of the current location" leaves too
> > much unsaid. The reader will wonder why does location matter for this
> > purpose. I suggest to make that explicit in the text.
>
> I'm not sure how to word it nor exactly what you are looking for.
> How about the following for the gdb/doc/gdb.texinfo piece:
Sounds good to me.
> Thanks for reviewing the doc changes so quickly.
Thanks for working on this in the first place.
next prev parent reply other threads:[~2014-11-11 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 21:41 David Taylor
2014-11-11 3:44 ` Eli Zaretskii
2014-11-11 14:01 ` David Taylor
2014-11-11 15:41 ` Eli Zaretskii [this message]
2014-11-19 21:00 ` RFA info macro [-at LOCATION,] (v2) David Taylor
2014-11-19 21:20 ` Eli Zaretskii
2014-11-20 2:38 ` Doug Evans
[not found] ` <001a1132e59ca4575e0508413955@google.com>
[not found] ` <CAP9bCMRJr4Fbunbnt-93FYnWUgDqjaLWZ731_rZp-JP8qkKf=w@mail.gmail.com>
2014-11-20 14:58 ` Fwd: Delivery Status Notification (Failure) David Taylor
2014-11-23 19:18 ` Doug Evans
2014-11-23 20:00 ` 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=83lhnhn3se.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dtaylor@usendtaylorx2l.lss.emc.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).