public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>
Cc: gdb-patches@sourceware.org, sergiodj@redhat.com
Subject: Re: [ping^3 PATCH v2 1/4] Implemement support for groups of syscalls in the xml-syscall interface.
Date: Mon, 12 Jan 2015 20:47:00 -0000	[thread overview]
Message-ID: <21684.13007.526850.693145@ruffy2.mtv.corp.google.com> (raw)
In-Reply-To: <87y4q1c7uu.fsf_-_@krisman.be>

Gabriel Krisman Bertazi writes:
 > Gabriel Krisman Bertazi <gabriel@krisman.be> writes:
 > 
 > > Gabriel Krisman Bertazi <gabriel@krisman.be> writes:
 > >
 > >>> Is this good to go?
 > >>>
 > >>
 > >> Ping. :)
 > >
 > > ping^2
 > 
 > ping^3
 > 
 > Heh. Missed a few weekly pings.  Do you guys think we might get this
 > upstream anytime soon?
 > 
 > Thanks,
 > 
 > -- 
 > Gabriel Krisman Bertazi

Hi.

Sorry for the delay.

It's on my list to get reviewed this week.
Please ping me directly if you don't hear from me by Thursday.

[And thanks Sergio for the heads up!]

  reply	other threads:[~2015-01-12 20:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 19:05 [PATCH " Gabriel Krisman Bertazi
2014-11-02 19:36 ` [PATCH 0/4] Catch syscall groups Gabriel Krisman Bertazi
2014-11-02 19:36   ` [PATCH 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-14 22:55     ` Sergio Durigan Junior
2014-11-02 19:36   ` [PATCH 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-11-14 22:42     ` Sergio Durigan Junior
2014-11-02 19:37   ` [PATCH 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-02 19:45     ` Eli Zaretskii
2014-11-12  2:04       ` Gabriel Krisman Bertazi
2014-11-12  3:48         ` Eli Zaretskii
2014-11-14 18:52           ` Gabriel Krisman Bertazi
2014-11-14 20:38             ` Eli Zaretskii
2014-11-03 18:38     ` Sergio Durigan Junior
2014-11-02 19:37   ` [PATCH 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2014-11-14 23:00     ` Sergio Durigan Junior
2014-11-20  2:11       ` Gabriel Krisman Bertazi
2014-11-20  3:08         ` Sergio Durigan Junior
2014-11-21 19:05   ` [PATCH v2 2/4] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2014-11-21 21:34     ` Sergio Durigan Junior
2015-01-15  8:12     ` Doug Evans
2014-11-21 19:06   ` [PATCH v2 4/4] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2014-11-21 19:48     ` Eli Zaretskii
2014-11-26  3:58       ` Gabriel Krisman Bertazi
2014-11-21 19:06   ` [PATCH v2 3/4] Create syscall groups for x86_64 Gabriel Krisman Bertazi
2015-01-15  8:28     ` Doug Evans
2014-11-29  0:19 ` [ping PATCH v2 1/4] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2014-12-08  0:09   ` [ping^2 " Gabriel Krisman Bertazi
2014-12-21 15:59     ` [ping^3 " Gabriel Krisman Bertazi
2015-01-12 20:47       ` Doug Evans [this message]
2015-01-15  8:03 ` [PATCH " Doug Evans
2015-01-29  4:43   ` Gabriel Krisman Bertazi
2015-01-29  7:42     ` 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=21684.13007.526850.693145@ruffy2.mtv.corp.google.com \
    --to=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).