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-9995] libstdc++: Fix "extact" typos in comments
Date: Tue, 16 Apr 2024 15:46:38 +0000 (GMT)	[thread overview]
Message-ID: <20240416154638.E6ED53858D35@sourceware.org> (raw)

https://gcc.gnu.org/g:443748259d903b6f4d4557392fc788df93d63377

commit r14-9995-g443748259d903b6f4d4557392fc788df93d63377
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 16 10:56:46 2024 +0100

    libstdc++: Fix "extact" typos in comments
    
    libstdc++-v3/ChangeLog:
    
            * config/locale/dragonfly/numeric_members.cc: Fix typos in
            comments.
            * config/locale/gnu/numeric_members.cc: Likewise.

Diff:
---
 libstdc++-v3/config/locale/dragonfly/numeric_members.cc | 4 ++--
 libstdc++-v3/config/locale/gnu/numeric_members.cc       | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/config/locale/dragonfly/numeric_members.cc b/libstdc++-v3/config/locale/dragonfly/numeric_members.cc
index 4e8364f6f44..dc71ef4ed70 100644
--- a/libstdc++-v3/config/locale/dragonfly/numeric_members.cc
+++ b/libstdc++-v3/config/locale/dragonfly/numeric_members.cc
@@ -115,7 +115,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	    }
 	}
 
-      // NB: There is no way to extact this info from posix locales.
+      // NB: There is no way to extract this info from posix locales.
       // _M_truename = __nl_langinfo_l(YESSTR, __cloc);
       _M_data->_M_truename = "true";
       _M_data->_M_truename_size = 4;
@@ -213,7 +213,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	    }
 	}
 
-      // NB: There is no way to extact this info from posix locales.
+      // NB: There is no way to extract this info from posix locales.
       // _M_truename = __nl_langinfo_l(YESSTR, __cloc);
       _M_data->_M_truename = L"true";
       _M_data->_M_truename_size = 4;
diff --git a/libstdc++-v3/config/locale/gnu/numeric_members.cc b/libstdc++-v3/config/locale/gnu/numeric_members.cc
index 3d1a88ae832..f061065922f 100644
--- a/libstdc++-v3/config/locale/gnu/numeric_members.cc
+++ b/libstdc++-v3/config/locale/gnu/numeric_members.cc
@@ -159,7 +159,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	    }
 	}
 
-      // NB: There is no way to extact this info from posix locales.
+      // NB: There is no way to extract this info from posix locales.
       // _M_truename = __nl_langinfo_l(YESSTR, __cloc);
       _M_data->_M_truename = "true";
       _M_data->_M_truename_size = 4;
@@ -251,7 +251,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	    }
 	}
 
-      // NB: There is no way to extact this info from posix locales.
+      // NB: There is no way to extract this info from posix locales.
       // _M_truename = __nl_langinfo_l(YESSTR, __cloc);
       _M_data->_M_truename = L"true";
       _M_data->_M_truename_size = 4;

                 reply	other threads:[~2024-04-16 15:46 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=20240416154638.E6ED53858D35@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).