From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Remove obsolete comment in <string>
Date: Sat, 9 Jul 2022 16:46:35 +0100 [thread overview]
Message-ID: <CACb0b4nmF=csyGtPVxafAX51oz528g4-tPU_yiLw=Za7=+ZbqA@mail.gmail.com> (raw)
In-Reply-To: <a7dc6260-d1af-95fc-c8db-0419c7dee5a3@gmail.com>
On Sat, 9 Jul 2022 at 13:26, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> libstdc++: Remove obsolete comment in <string> header
>
> The comment is obsolete because char_traits.h do not include
> stl_algobase.h
> anymore and stl_algobase.h is included directly from <string> a few
> lines
> below.
Nice, thanks
>
> libstdc++-v3/ChangeLog:
>
> * include/std/string: Remove obsolete comment about
> char_traits.h including
> stl_algobase.h.
>
> François
prev parent reply other threads:[~2022-07-09 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:25 François Dumont
2022-07-09 15:46 ` Jonathan Wakely [this message]
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='CACb0b4nmF=csyGtPVxafAX51oz528g4-tPU_yiLw=Za7=+ZbqA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).