From: "Marc Poulhiès" <poulhies@adacore.com>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Simon Wright <simon@pushface.org>,
gcc-patches@gcc.gnu.org, squirek@adacore.com
Subject: Re: [PATCH] Fix PR ada/111813 (Inconsistent limit in Ada.Calendar.Formatting)
Date: Thu, 09 Nov 2023 14:04:30 +0100 [thread overview]
Message-ID: <87fs1f9iim.fsf@adacore.com> (raw)
In-Reply-To: <20231109112538.GA2659993@adacore.com>
Arnaud Charlet <charlet@adacore.com> writes:
> Marc, can you please take care of it when you get a chance?
I'll push the change as soon as the tests are finished.
Marc
next prev parent reply other threads:[~2023-11-09 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:32 Simon Wright
2023-10-19 11:31 ` Simon Wright
2023-10-19 12:13 ` Arnaud Charlet
2023-10-24 9:49 ` Arnaud Charlet
2023-11-09 11:22 ` Simon Wright
2023-11-09 11:25 ` Arnaud Charlet
2023-11-09 13:04 ` Marc Poulhiès [this message]
2023-11-09 14:01 ` 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=87fs1f9iim.fsf@adacore.com \
--to=poulhies@adacore.com \
--cc=charlet@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=simon@pushface.org \
--cc=squirek@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).