From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2181) id 95B933858D20; Thu, 25 Apr 2024 17:44:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 95B933858D20 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1714067046; bh=PaOBYvBdEBHtgif4sFQhvsCAjCzYAbIYXsUyT5szNRg=; h=From:To:Subject:Date:From; b=pq/7giSxjL4spnIUJ7+6r/0SL/WmdxKMDFWVc9QZPjYuwkxEbzNVBwv3oaXcNRCkB mW5h3FgsMg0qANZffKcbDlloiEJE2Kmn3qeypMhCZiAnZHEzQH/VmFvsNhp9onYQLn o3WK60P55MipUbt7wrQegvBk7ShJc/57aspn9XZ4= MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" From: Jonathan Wakely To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r14-10128] libstdc++: Fix typo in Doxygen comment X-Act-Checkin: gcc X-Git-Author: Jonathan Wakely X-Git-Refname: refs/heads/master X-Git-Oldrev: c9cc1c850c6d084752207b6cf247a0a48bae0d52 X-Git-Newrev: 6391cf8bd9c1d71805d9aba00b25fdaa550f39c8 Message-Id: <20240425174406.95B933858D20@sourceware.org> Date: Thu, 25 Apr 2024 17:44:06 +0000 (GMT) List-Id: https://gcc.gnu.org/g:6391cf8bd9c1d71805d9aba00b25fdaa550f39c8 commit r14-10128-g6391cf8bd9c1d71805d9aba00b25fdaa550f39c8 Author: Jonathan Wakely 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