public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Thu, 19 Jan 2023 20:24:05 +0000 (GMT)	[thread overview]
Message-ID: <20230119202405.868423858416@sourceware.org> (raw)

https://gcc.gnu.org/g:8787039dbe03a6817c35815c11ace6194673ca94

commit 8787039dbe03a6817c35815c11ace6194673ca94
Merge: 1184c551867 61ef24af3ce
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Jan 19 21:23:08 2023 +0100

    Merge branch 'releases/gcc-12' into devel/omp/gcc-12
    
    Merge up to r12-9052-g61ef24af3ce8ec9c5eb65770f8047d98f42a93bf (19th Jan 2023)

Diff:

 gcc/DATESTAMP                                   |    2 +-
 libcpp/po/ChangeLog                             |    4 +
 libcpp/po/ka.po                                 | 1110 +++++++++++++++++++++++
 libstdc++-v3/ChangeLog                          |   24 +
 libstdc++-v3/include/bits/atomic_wait.h         |   42 +-
 libstdc++-v3/src/c++11/compatibility-condvar.cc |   22 +-
 6 files changed, 1180 insertions(+), 24 deletions(-)

             reply	other threads:[~2023-01-19 20:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 20:24 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-27 16:34 Tobias Burnus
2023-02-20  6:52 Tobias Burnus
2023-02-13  9:21 Tobias Burnus
2023-02-06  7:42 Tobias Burnus
2023-01-09  9:21 Tobias Burnus
2022-12-27 10:54 Tobias Burnus
2022-12-21 18:21 Tobias Burnus
2022-12-19 17:32 Tobias Burnus
2022-11-25 10:37 Tobias Burnus
2022-11-18  9:48 Tobias Burnus
2022-11-14 15:41 Tobias Burnus
2022-10-24 10:21 Tobias Burnus
2022-10-11  8:26 Tobias Burnus
2022-09-29 14:45 Tobias Burnus
2022-09-23  8:48 Tobias Burnus
2022-09-09 13:39 Tobias Burnus
2022-08-31  6:14 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-01 18:13 Kwok Yeung

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=20230119202405.868423858416@sourceware.org \
    --to=burnus@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).