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 r14-10128] libstdc++: Fix typo in Doxygen comment
Date: Thu, 25 Apr 2024 17:44:06 +0000 (GMT)	[thread overview]
Message-ID: <20240425174406.95B933858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:6391cf8bd9c1d71805d9aba00b25fdaa550f39c8

commit r14-10128-g6391cf8bd9c1d71805d9aba00b25fdaa550f39c8
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Apr 25 13:52:00 2024 +0100

    libstdc++: Fix typo in Doxygen comment
    
    libstdc++-v3/ChangeLog:
    
            * include/std/chrono (tzdb_list): Fix typo in Doxygen comment.

Diff:
---
 libstdc++-v3/include/std/chrono | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index 3a9751781d2..b0aadf83b03 100644
--- a/libstdc++-v3/include/std/chrono
+++ b/libstdc++-v3/include/std/chrono
@@ -2780,7 +2780,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 
       /** Remove the tzdb object _after_ the one the iterator refers to.
        *
-       * Calling this function concurently with any of `front()`, `begin()`,
+       * Calling this function concurrently with any of `front()`, `begin()`,
        * or `end()` does not cause a data race, but in general this function
        * is not thread-safe. The behaviour may be undefined if erasing an
        * element from the list while another thread is calling the same

                 reply	other threads:[~2024-04-25 17:44 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=20240425174406.95B933858D20@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).