public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Wai <richard@annexi-strayline.com>
To: "Marc Poulhiès" <poulhies@adacore.com>
Cc: Arnaud Charlet <charlet@adacore.com>,
	 Eric Botcazou <ebotcazou@adacore.com>,
	 Stephen Baird <baird@adacore.com>,
	 Gary Dismukes <dismukes@adacore.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2 v3] Ada: Synchronized private extensions are always limited
Date: Tue, 19 Sep 2023 03:40:26 +0000	[thread overview]
Message-ID: <010d018aab866671-d9917985-9044-42df-a441-de80df28c3b4-000000@ca-central-1.amazonses.com> (raw)
In-Reply-To: <87r0mv3m8s.fsf@adacore.com>

Hi Marc,

Indeed I have read and accept the terms of the DCO. Please proceed to apply these changes at your convenience.

Thanks for helping me get these committed!

Richard Wai

> On Sep 18, 2023, at 04:31, Marc Poulhiès <poulhies@adacore.com> wrote:
> 
> 
> Hello Richard,
> 
>> I have added the required “Signed-off-by” tag to the patch and to the change log
>> entry below. I believe for all other aspects I have followed the instructions.
> 
> Thanks for doing these modifications. I believe you have read the
> Developer's Certificate of Origin (https://gcc.gnu.org/dco.html) and
> accept it?
> 
>> For getting the patch applied it states "If you do not have write access and a
>> patch of yours has been approved, but not committed, please advise the approver
>> of that fact.” So I think I have done that correctly.. However let me know if
>> there is someone else not included in the CC that should be handling that.
> 
> I can take it from here and apply both your changes if that's ok with
> you.
> 
> Thanks for your patches!
> 
> Marc


  reply	other threads:[~2023-09-19  3:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 14:22 [PING][PATCH 1/2] " Richard Wai
2023-09-01 12:06 ` Arnaud Charlet
2023-09-01 12:08   ` Arnaud Charlet
2023-09-12 21:46     ` [PATCH 1/2 v2] " Richard Wai
2023-09-13  7:54       ` Arnaud Charlet
     [not found]         ` <010d018aa45bb0cf-8a7f2370-3e66-40b4-9ce4-c609f0532443-000000@ca-central-1.amazonses.com>
2023-09-18  8:31           ` [PATCH 1/2 v3] " Marc Poulhiès
2023-09-19  3:40             ` Richard Wai [this message]
2023-09-19 12:03               ` [COMMITTED] ada: Private extensions with the keyword "synchronized" " Marc Poulhiès

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=010d018aab866671-d9917985-9044-42df-a441-de80df28c3b4-000000@ca-central-1.amazonses.com \
    --to=richard@annexi-strayline.com \
    --cc=baird@adacore.com \
    --cc=charlet@adacore.com \
    --cc=dismukes@adacore.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=poulhies@adacore.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).