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 r11-5652] libstdc++: Fix indentation in rope Date: Wed, 2 Dec 2020 12:28:48 +0000 (GMT) [thread overview] Message-ID: <20201202122848.3C2CB395BC03@sourceware.org> (raw) https://gcc.gnu.org/g:d38fbb5a863dfc00631c74a525a908cef620e149 commit r11-5652-gd38fbb5a863dfc00631c74a525a908cef620e149 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Dec 2 11:25:42 2020 +0000 libstdc++: Fix indentation in rope libstdc++-v3/ChangeLog: * include/ext/rope: Fix indentation of access specifiers. Diff: --- libstdc++-v3/include/ext/rope | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/include/ext/rope b/libstdc++-v3/include/ext/rope index 08e510bb0dc..8479acd8f74 100644 --- a/libstdc++-v3/include/ext/rope +++ b/libstdc++-v3/include/ext/rope @@ -675,7 +675,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION static void _S_ref(_Rope_RopeRep*) { } static void _S_free_if_unref(_Rope_RopeRep*) { } # endif -protected: + protected: _Rope_RopeRep& operator=(const _Rope_RopeRep&); @@ -742,7 +742,7 @@ protected: this->__STL_FREE_STRING(_M_data, this->_M_size, this->_M_get_allocator()); } #endif -protected: + protected: _Rope_RopeLeaf& operator=(const _Rope_RopeLeaf&); @@ -778,7 +778,7 @@ protected: _M_right->_M_unref_nonnil(); } #endif -protected: + protected: _Rope_RopeConcatenation& operator=(const _Rope_RopeConcatenation&); @@ -1508,7 +1508,7 @@ protected: __ROPE_DEFINE_ALLOCS(_Alloc) #undef __ROPE_DEFINE_ALLOC - protected: + protected: _Rope_base& operator=(const _Rope_base&);
reply other threads:[~2020-12-02 12:28 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=20201202122848.3C2CB395BC03@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: linkBe 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).