Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: davem@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc/rfa:doc] PC_IN_SIGTRAMP; Was: [RFA] Multi-arch IN_SIGTRAMP
Date: Sun, 21 Apr 2002 12:16:00 -0000	[thread overview]
Message-ID: <8011-Sun21Apr2002221607+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3CC2FA04.50605@cygnus.com> (message from Andrew Cagney on Sun, 21 Apr 2002 13:42:28 -0400)

> Date: Sun, 21 Apr 2002 13:42:28 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> [Eli, note the doco update]

Thanks for the heads-up.

> 	* gdbint.texinfo (Target Architecture Definition): Replace
> 	IN_SIGTRAMP with PC_IN_SIGTRAMP.

Approved, with a few minor comments:

> +@item PC_IN_SIGTRAMP (@var{pc}, @var{name})
> +@findex PC_IN_SIGTRAMP
> +Sigtramp is a routine that the kernel calls

Here you introduce a new term.  It is best to give it a @dfn markup,
so that it stands out, and add an index entry for it, so that someone
who bumps into this term elsewhere in the manual could find its
definition.  So:

  @item PC_IN_SIGTRAMP (@var{pc}, @var{name})
  @findex PC_IN_SIGTRAMP
  @cindex sigtramp
  A @dfn{sigtramp} is a routine that the kernel calls...

> +This function, given a program counter value and the (possibly NULL)

"NULL" should be in @code, since it's a C symbol.

Also, it's better to say "... given a program counter value in
@var{pc}...", since this immediately explains what is @var{pc}.

Thanks.


  reply	other threads:[~2002-04-21 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21  1:20 David S. Miller
2002-04-21 10:42 ` [rfc/rfa:doc] PC_IN_SIGTRAMP; Was: " Andrew Cagney
2002-04-21 12:16   ` Eli Zaretskii [this message]
2002-04-24  9:23     ` Andrew Cagney
2002-04-21 16:55   ` David S. Miller

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-Sun21Apr2002221607+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=davem@redhat.com \
    --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