From: Eli Zaretskii <eliz@gnu.org>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
sergiodj@redhat.com, dje@google.com
Subject: Re: [PATCH v5 5/5] Update documentation on catching a group of related syscalls.
Date: Mon, 16 May 2016 02:30:00 -0000 [thread overview]
Message-ID: <83eg9268g9.fsf@gnu.org> (raw)
In-Reply-To: <1463344320-6439-6-git-send-email-gabriel@krisman.be> (message from Gabriel Krisman Bertazi on Sun, 15 May 2016 17:32:00 -0300)
> From: Gabriel Krisman Bertazi <gabriel@krisman.be>
> Cc: palves@redhat.com, sergiodj@redhat.com, dje@google.com, Gabriel Krisman Bertazi <gabriel@krisman.be>
> Date: Sun, 15 May 2016 17:32:00 -0300
>
> Eli approved this on a previous version.
There's one typo to correct:
> +You may specify a group of related syscalls to be caught at once using
> +the @code{group:} syntax (@code{g:} is a shorter equivalent.). For
^
Redundant period inside the parentheses.
Thanks.
next prev parent reply other threads:[~2016-05-16 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 20:32 [PATCH v5 0/5] Catch syscall groups Gabriel Krisman Bertazi
2016-05-15 20:32 ` [PATCH v5 3/5] Add tests for catching groups of syscalls on supported architectures Gabriel Krisman Bertazi
2016-05-15 20:32 ` [PATCH v5 5/5] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2016-05-16 2:30 ` Eli Zaretskii [this message]
2016-05-15 20:32 ` [PATCH v5 2/5] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2016-05-15 20:32 ` [PATCH v5 1/5] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2016-05-15 20:32 ` [PATCH v5 4/5] Include group information to xml syscall files Gabriel Krisman Bertazi
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=83eg9268g9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@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