Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Fix amd64->i386 linux syscall restart problem
Date: Thu, 11 Apr 2019 00:16:00 -0000	[thread overview]
Message-ID: <20190410171606.0e736077@f29-4.lan> (raw)
In-Reply-To: <bc353e59-f640-2d09-8a71-984f0102733e@redhat.com>

On Wed, 10 Apr 2019 12:42:30 +0100
Pedro Alves <palves@redhat.com> wrote:

> > Below is a diff showing the new comments.  It also includes the
> > changes which wrap the multi-line expressions in parens.  
> 
> Thanks, that new version of the comment looks great.

It's in now.  Thanks for the review.

Kevin


  reply	other threads:[~2019-04-11  0:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17  5:13 Kevin Buettner
2019-04-04 16:51 ` Kevin Buettner
2019-04-09 17:46 ` Pedro Alves
2019-04-10  2:29   ` Kevin Buettner
2019-04-10 11:42     ` Pedro Alves
2019-04-11  0:16       ` Kevin Buettner [this message]
2019-05-21 12:59         ` Tom de Vries
2019-06-21  6:34           ` [PING][PATCH] " Tom de Vries
2019-07-08 17:00             ` Kevin Buettner
2019-07-12 11:42               ` Tom de Vries
2019-07-12 12:24                 ` Kevin Buettner

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=20190410171606.0e736077@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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