From: Eli Zaretskii <eliz@gnu.org>
To: Don Breazeal <donb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v7 7/7] Extended-remote follow fork documentation
Date: Fri, 10 Apr 2015 17:56:00 -0000 [thread overview]
Message-ID: <83wq1jsw8m.fsf@gnu.org> (raw)
In-Reply-To: <1428685786-18094-8-git-send-email-donb@codesourcery.com>
> From: Don Breazeal <donb@codesourcery.com>
> Date: Fri, 10 Apr 2015 10:09:46 -0700
>
> This patch contains the accumulated documentation changes for the
> rest of the extended-remote follow fork patchset.
Thanks.
> gdb/NEWS | 24 ++++++++++++++++
This part is OK.
> +@cindex fork events, remote reply
> +@item fork
> +The packet indicates that @code{fork} was called, and @var{r}
What does that @var{r} refer to? The previous text mentions
@var{n}:@var{r} pairs, but there's no @var{n} in this description, so
it doesn't seem to fit. What am I missing?
> +shared. The @var{r} part is ignored. This packet is only
^^
Two spaces.
OK with those fixed.
next prev parent reply other threads:[~2015-04-10 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 17:09 [PATCH v7 0/7] Remote fork events Don Breazeal
2015-04-10 17:10 ` [PATCH v7 3/7] Extended-remote Linux follow fork Don Breazeal
2015-04-15 15:38 ` Pedro Alves
2015-04-10 17:10 ` [PATCH v7 1/7] Identify remote fork event support Don Breazeal
2015-04-15 15:37 ` Pedro Alves
2015-04-10 17:10 ` [PATCH v7 4/7] Arch-specific remote follow fork Don Breazeal
2015-04-10 17:10 ` [PATCH v7 2/7] Clone remote breakpoints Don Breazeal
2015-04-10 17:11 ` [PATCH v7 7/7] Extended-remote follow fork documentation Don Breazeal
2015-04-10 17:56 ` Eli Zaretskii [this message]
2015-04-10 18:15 ` Breazeal, Don
2015-04-10 18:29 ` Eli Zaretskii
2015-04-10 20:43 ` Don Breazeal
2015-04-15 15:47 ` Pedro Alves
2015-04-10 17:11 ` [PATCH v7 5/7] Remote follow vfork Don Breazeal
2015-04-15 15:38 ` Pedro Alves
2015-04-15 15:41 ` Pedro Alves
2015-04-10 17:11 ` [PATCH v7 6/7] Remote fork catch Don Breazeal
2015-04-15 15:39 ` Pedro Alves
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=83wq1jsw8m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=donb@codesourcery.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