Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Alan Hayward <alan.hayward@arm.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] LONGEST and ULONGEST function template instantiation
Date: Fri, 16 Jun 2017 14:46:00 -0000	[thread overview]
Message-ID: <CAH=s-PPVoKFX-vWzmKtY=ZT2=0Gpk0JLfXPX-VpoLQuUrLokeA@mail.gmail.com> (raw)
In-Reply-To: <d8b11d42-54ab-96da-786a-f535fb057077@redhat.com>

On Thu, Jun 15, 2017 at 5:19 PM, Pedro Alves <palves@redhat.com> wrote:
> On 06/15/2017 12:59 PM, Yao Qi wrote:
>> Pedro Alves <palves@redhat.com> writes:
>>
>> Hi Pedro,
>> I pick up your patch, and update the ChangeLog entry.
>
> Thanks.  FAOD, fine with me to push it in.
>

Patch is pushed in.

-- 
Yao (齐尧)


      reply	other threads:[~2017-06-16 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 11:29 Yao Qi
2017-06-13 11:33 ` Yao Qi
2017-06-14 13:54   ` Alan Hayward
2017-06-14 16:12 ` Pedro Alves
2017-06-15 11:59   ` Yao Qi
2017-06-15 16:19     ` Pedro Alves
2017-06-16 14:46       ` Yao Qi [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='CAH=s-PPVoKFX-vWzmKtY=ZT2=0Gpk0JLfXPX-VpoLQuUrLokeA@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=alan.hayward@arm.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