public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tamar Christina <tnfchris@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ARM/heads/arm-perf-staging)] libstdc++: Fix author in previous ChangeLog entry
Date: Fri, 17 Jul 2020 14:08:48 +0000 (GMT)	[thread overview]
Message-ID: <20200717140848.7B2E43A1902D@sourceware.org> (raw)

https://gcc.gnu.org/g:9673d11ec53bda9ea7c437f5ce8fb93797f48ab9

commit 9673d11ec53bda9ea7c437f5ce8fb93797f48ab9
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Mar 25 22:20:42 2020 +0000

    libstdc++: Fix author in previous ChangeLog entry
    
    The previous commit added two tests which were written by Mike Crowe,
    not by me. This fixes the ChangeLog entry.

Diff:
---
 libstdc++-v3/ChangeLog | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 11f7f02eb0b..039eb55939f 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,10 +1,12 @@
-2020-03-25  Jonathan Wakely  <jwakely@redhat.com>
+2020-03-25  Mike Crowe  <mac@mcrowe.com>
 
 	* testsuite/30_threads/shared_timed_mutex/try_lock_until/1.cc: New
 	test.
 	* testsuite/30_threads/shared_timed_mutex/try_lock_until/2.cc: New
 	test.
 
+2020-03-25  Jonathan Wakely  <jwakely@redhat.com>
+
 	* include/bits/fs_fwd.h (filesystem::__file_clock): Move to ...
 	* include/std/chrono (filesystem::__file_clock): Here.
 	(filesystem::__file_clock::from_sys, filesystem::__file_clock::to_sys):


                 reply	other threads:[~2020-07-17 14:08 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=20200717140848.7B2E43A1902D@sourceware.org \
    --to=tnfchris@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).