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 r10-9677] libstdc++: Remove spurious line break in doxygen comment
Date: Fri,  9 Apr 2021 15:14:53 +0000 (GMT)	[thread overview]
Message-ID: <20210409151453.1739D398EC1F@sourceware.org> (raw)

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

commit r10-9677-gd7fa35db13d2523155034c444858bb1ae4eedc0e
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Apr 8 23:39:29 2021 +0100

    libstdc++: Remove spurious line break in doxygen comment
    
    libstdc++-v3/ChangeLog:
    
            * include/bits/basic_string.h: Tweak doxygen comment.
    
    (cherry picked from commit 96292c3e3439aa167ed7ae595f89b8776e705897)

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

diff --git a/libstdc++-v3/include/bits/basic_string.h b/libstdc++-v3/include/bits/basic_string.h
index ab9fb04c451..f36bd6a4fe6 100644
--- a/libstdc++-v3/include/bits/basic_string.h
+++ b/libstdc++-v3/include/bits/basic_string.h
@@ -4674,8 +4674,7 @@ _GLIBCXX_END_NAMESPACE_CXX11
        *  @brief  Insert a string_view.
        *  @param __pos1  Position in string to insert at.
        *  @param __svt   The object convertible to string_view to insert from.
-       *  @param __pos2  Position in string_view to insert
-       *  from.
+       *  @param __pos2  Position in string_view to insert from.
        *  @param __n    The number of characters to insert.
        *  @return  Reference to this string.
       */


                 reply	other threads:[~2021-04-09 15:14 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=20210409151453.1739D398EC1F@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).