public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r11-9150] libstdc++: Rename files with the wrong extensions Date: Wed, 13 Oct 2021 23:38:49 +0000 (GMT) [thread overview] Message-ID: <20211013233849.89A9D3858403@sourceware.org> (raw) https://gcc.gnu.org/g:c706d5c3b82bd18b8a870e3a8a3508ddc875da0b commit r11-9150-gc706d5c3b82bd18b8a870e3a8a3508ddc875da0b Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Oct 13 22:31:51 2021 +0100 libstdc++: Rename files with the wrong extensions libstdc++-v3/ChangeLog: * testsuite/27_io/filesystem/path/construct/102592.C: Moved to... * testsuite/27_io/filesystem/path/construct/102592.cc: ...here. * testsuite/28_regex/match_results/102667.C: Moved to... * testsuite/28_regex/match_results/102667.cc: ...here. (cherry picked from commit ce55693604813c5be7d23260f1fd276cf5a48f8f) Diff: --- .../testsuite/27_io/filesystem/path/construct/{102592.C => 102592.cc} | 0 libstdc++-v3/testsuite/28_regex/match_results/{102667.C => 102667.cc} | 0 2 files changed, 0 insertions(+), 0 deletions(-) diff --git a/libstdc++-v3/testsuite/27_io/filesystem/path/construct/102592.C b/libstdc++-v3/testsuite/27_io/filesystem/path/construct/102592.cc similarity index 100% rename from libstdc++-v3/testsuite/27_io/filesystem/path/construct/102592.C rename to libstdc++-v3/testsuite/27_io/filesystem/path/construct/102592.cc diff --git a/libstdc++-v3/testsuite/28_regex/match_results/102667.C b/libstdc++-v3/testsuite/28_regex/match_results/102667.cc similarity index 100% rename from libstdc++-v3/testsuite/28_regex/match_results/102667.C rename to libstdc++-v3/testsuite/28_regex/match_results/102667.cc
reply other threads:[~2021-10-13 23:38 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211013233849.89A9D3858403@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@gcc.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: linkBe 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).