Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	Mark Kettenis <kettenis@gnu.org>
Subject: Re: [PATCH] Split i386_stap_parse_special_token into smaller functions
Date: Sun, 12 Jan 2014 03:36:00 -0000	[thread overview]
Message-ID: <m3r48dj2hn.fsf@redhat.com> (raw)
In-Reply-To: <20140111030200.GD4762@adacore.com> (Joel Brobecker's message of	"Sat, 11 Jan 2014 07:02:00 +0400")

On Saturday, January 11 2014, Joel Brobecker wrote:

> Go ahead and push. I reviewed the patch a second time, and it still
> looks good to me.

Thanks, Joel.  Checked in:

  https://sourceware.org/ml/gdb-cvs/2014-01/msg00045.html

-- 
Sergio


      reply	other threads:[~2014-01-12  3:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-29  5:43 Sergio Durigan Junior
2013-12-30  3:11 ` Joel Brobecker
2013-12-30  5:38   ` Sergio Durigan Junior
2014-01-06 15:34   ` Sergio Durigan Junior
2014-01-11  1:52     ` Sergio Durigan Junior
2014-01-11  3:02       ` Joel Brobecker
2014-01-12  3:36         ` Sergio Durigan Junior [this message]

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=m3r48dj2hn.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@gnu.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