From: Pedro Alves <palves@redhat.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>, gdb-patches@sourceware.org
Cc: sergiodj@redhat.com, dje@google.com
Subject: Re: [PATCH v7 0/5] Catch syscall group
Date: Thu, 30 Jun 2016 16:10:00 -0000 [thread overview]
Message-ID: <4754240c-e5c3-343e-b107-c9552cac552f@redhat.com> (raw)
In-Reply-To: <1466368449-26477-1-git-send-email-gabriel@krisman.be>
On 06/19/2016 09:34 PM, Gabriel Krisman Bertazi wrote:
> Changes since v6:
> - Initialize variable to NULL (Sergio)
> - Create wrapper rules syscalls-xml and clean-syscalls-xml (Pedro)
> - Always check for xsltproc in configure.ac. Only force the dependency
> when in maintainer mode.
> - Expose xml creation rule outside of maintainer mode (Pedro)
> - Fix up license header in apply-defaults.xsl (Pedro)
Thanks. I'm happy with the updates. LGTM.
--
Pedro Alves
next prev parent reply other threads:[~2016-06-30 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 20:34 Gabriel Krisman Bertazi
2016-06-19 20:34 ` [PATCH v7 3/5] Add tests for catching groups of syscalls on supported architectures Gabriel Krisman Bertazi
2016-06-19 20:34 ` [PATCH v7 1/5] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2016-06-19 20:34 ` [PATCH v7 2/5] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2016-06-19 20:35 ` [PATCH v7 5/5] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2016-06-19 20:43 ` [RESEND PATCH v7 4/5] Include group information to xml syscall files Gabriel Krisman Bertazi
2016-06-30 16:10 ` Pedro Alves [this message]
2016-07-13 1:45 ` [PATCH v7 0/5] Catch syscall group Gabriel Krisman Bertazi
2016-07-13 17:34 ` Doug Evans
2016-07-23 21:44 ` Gabriel Krisman Bertazi
2016-06-27 18:54 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=4754240c-e5c3-343e-b107-c9552cac552f@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).