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 r12-3199] libstdc++: Fix comment typo
Date: Sat, 28 Aug 2021 12:07:16 +0000 (GMT)	[thread overview]
Message-ID: <20210828120716.0E0D9385703F@sourceware.org> (raw)

https://gcc.gnu.org/g:dd3e5859fc16701acb73f59220c8c964af9f713b

commit r12-3199-gdd3e5859fc16701acb73f59220c8c964af9f713b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Aug 27 22:10:43 2021 +0100

    libstdc++: Fix comment typo
    
    Signed-off-by: Jonathan Wakely <jwakely@redhat.com>
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/stl_uninitialized.h: Fix typo in comment.

Diff:
---
 libstdc++-v3/include/bits/stl_uninitialized.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/bits/stl_uninitialized.h b/libstdc++-v3/include/bits/stl_uninitialized.h
index ddc1405cb0e..2fee1e17f00 100644
--- a/libstdc++-v3/include/bits/stl_uninitialized.h
+++ b/libstdc++-v3/include/bits/stl_uninitialized.h
@@ -162,7 +162,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	_ValueType2;
 
       // _ValueType1 must be trivially-copyable to use memmove, so don't
-      // both optimizing to std::copy if it isn't.
+      // bother optimizing to std::copy if it isn't.
       // XXX Unnecessary because std::copy would check it anyway?
       const bool __can_memmove = __is_trivial(_ValueType1);


                 reply	other threads:[~2021-08-28 12:07 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=20210828120716.0E0D9385703F@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).