From: Jonathan Wakely <jwakely@redhat.com>
To: Thomas Rodgers <rodgert@appliantology.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org, trodgers@redhat.com
Subject: Re: [PATCH] libstdc++: Add c++2a <syncstream>
Date: Wed, 21 Oct 2020 18:34:43 +0100 [thread overview]
Message-ID: <20201021173443.GB1037369@redhat.com> (raw)
In-Reply-To: <20201021165344.2412936-1-rodgert@appliantology.com>
On 21/10/20 09:53 -0700, Thomas Rodgers wrote:
>From: Thomas Rodgers <trodgers@redhat.com>
>
>libstdc++/Changelog:
> libstdc++-v3/doc/doxygen/user.cfg.in (INPUT): Add new header.
> libstdc++-v3/include/Makefile.am (std_headers): Add new header.
> libstdc++-v3/include/Makefile.in: Regenerate.
> libstdc++-v3/include/precompiled/stdc++.h: Include new header.
> libstdc++-v3/include/std/streambuf
> (__detail::__streambuf_core_access): Define.
> (basic_streambuf): Befriend __detail::__streambuf_core_access.
This file is no longer part of the commit, so the server will reject
this changelog. Please ensure the changelog is accurate (the
gcc-verify alias created by contrib/gcc-git-customization.sh can do
that) and push, thanks.
next prev parent reply other threads:[~2020-10-21 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 14:46 Thomas Rodgers
2020-10-15 18:13 ` Jonathan Wakely
2020-10-15 18:18 ` Jonathan Wakely
2020-10-15 19:29 ` Jonathan Wakely
2020-10-16 0:24 ` Thomas Rodgers
2020-10-21 16:53 ` Thomas Rodgers
2020-10-21 17:34 ` Jonathan Wakely [this message]
2020-10-21 19:39 ` Thomas Rodgers
2020-10-29 16:18 ` Jonathan Wakely
2020-10-29 21:12 ` Thomas Rodgers
2020-11-02 15:58 ` Thomas Rodgers
2020-11-02 16:10 ` Thomas Rodgers
2020-11-02 17:38 ` Jonathan Wakely
2020-11-02 18:43 ` Thomas Rodgers
2020-11-03 21:22 ` Christophe Lyon
2020-11-03 22:00 ` Jonathan Wakely
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=20201021173443.GB1037369@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=rodgert@appliantology.com \
--cc=trodgers@redhat.com \
/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).