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 r13-772] libstdc++: Remove redundancy in test pathnames
Date: Thu, 26 May 2022 09:18:35 +0000 (GMT)	[thread overview]
Message-ID: <20220526091835.5A2BC3834E77@sourceware.org> (raw)

https://gcc.gnu.org/g:f638f2b4b257386da05c77f300fe059235574295

commit r13-772-gf638f2b4b257386da05c77f300fe059235574295
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri May 20 10:26:07 2022 +0100

    libstdc++: Remove redundancy in test pathnames
    
    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.

Diff:
---
 .../requirements/{explicit_instantiation => }/explicit_instantiation.cc   | 0
 .../requirements/{explicit_instantiation => }/explicit_instantiation.cc   | 0
 .../requirements/{explicit_instantiation => }/explicit_instantiation.cc   | 0
 3 files changed, 0 insertions(+), 0 deletions(-)

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


                 reply	other threads:[~2022-05-26  9:18 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=20220526091835.5A2BC3834E77@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: 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).