public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r14-10128] libstdc++: Fix typo in Doxygen comment
@ 2024-04-25 17:44 Jonathan Wakely
0 siblings, 0 replies; only message in thread
From: Jonathan Wakely @ 2024-04-25 17:44 UTC (permalink / raw)
To: gcc-cvs, libstdc++-cvs
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-04-25 17:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-25 17:44 [gcc r14-10128] libstdc++: Fix typo in Doxygen comment Jonathan Wakely
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).