From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed 1/2] libstdc++: Remove redundancy in test pathnames
Date: Thu, 26 May 2022 10:20:29 +0100 [thread overview]
Message-ID: <20220526092030.1225077-1-jwakely@redhat.com> (raw)
Tested x86_64-linux, pushed to trunk.
-- >8 --
Repeating "explicit_instantiation" in these long pathnames is not
necessary.
libstdc++-v3/ChangeLog:
* testsuite/20_util/duration/requirements/explicit_instantiation/explicit_instantiation.cc:
Moved to...
* testsuite/20_util/duration/requirements/explicit_instantiation.cc: ...here.
* testsuite/20_util/time_point/requirements/explicit_instantiation/explicit_instantiation.cc:
Moved to...
* testsuite/20_util/time_point/requirements/explicit_instantiation.cc: ...here.
* testsuite/20_util/unique_ptr/requirements/explicit_instantiation/explicit_instantiation.cc:
Moved to...
* testsuite/20_util/unique_ptr/requirements/explicit_instantiation.cc: ...here.
---
.../{explicit_instantiation => }/explicit_instantiation.cc | 0
.../{explicit_instantiation => }/explicit_instantiation.cc | 0
.../{explicit_instantiation => }/explicit_instantiation.cc | 0
3 files changed, 0 insertions(+), 0 deletions(-)
rename libstdc++-v3/testsuite/20_util/duration/requirements/{explicit_instantiation => }/explicit_instantiation.cc (100%)
rename libstdc++-v3/testsuite/20_util/time_point/requirements/{explicit_instantiation => }/explicit_instantiation.cc (100%)
rename libstdc++-v3/testsuite/20_util/unique_ptr/requirements/{explicit_instantiation => }/explicit_instantiation.cc (100%)
diff --git a/libstdc++-v3/testsuite/20_util/duration/requirements/explicit_instantiation/explicit_instantiation.cc b/libstdc++-v3/testsuite/20_util/duration/requirements/explicit_instantiation.cc
similarity index 100%
rename from libstdc++-v3/testsuite/20_util/duration/requirements/explicit_instantiation/explicit_instantiation.cc
rename to libstdc++-v3/testsuite/20_util/duration/requirements/explicit_instantiation.cc
diff --git a/libstdc++-v3/testsuite/20_util/time_point/requirements/explicit_instantiation/explicit_instantiation.cc b/libstdc++-v3/testsuite/20_util/time_point/requirements/explicit_instantiation.cc
similarity index 100%
rename from libstdc++-v3/testsuite/20_util/time_point/requirements/explicit_instantiation/explicit_instantiation.cc
rename to libstdc++-v3/testsuite/20_util/time_point/requirements/explicit_instantiation.cc
diff --git a/libstdc++-v3/testsuite/20_util/unique_ptr/requirements/explicit_instantiation/explicit_instantiation.cc b/libstdc++-v3/testsuite/20_util/unique_ptr/requirements/explicit_instantiation.cc
similarity index 100%
rename from libstdc++-v3/testsuite/20_util/unique_ptr/requirements/explicit_instantiation/explicit_instantiation.cc
rename to libstdc++-v3/testsuite/20_util/unique_ptr/requirements/explicit_instantiation.cc
--
2.34.3
next reply other threads:[~2022-05-26 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 9:20 Jonathan Wakely [this message]
2022-05-26 9:20 ` [committed 2/2] libstdc++: Rename tests like .../wchar_t/1.cc to .../wchar_t.cc Jonathan Wakely
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=20220526092030.1225077-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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: 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).