From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
Date: Tue, 13 Apr 2021 16:19:11 +0100 [thread overview]
Message-ID: <CAH6eHdSOzMzcx_Xsx3g8X4-0cNNaA018dEtxWxghh88M+_=6Fw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1910250725560.3728@anthias.pfeifer.com>
Sorry for the slow reply ...
On Mon, 1 Feb 2021 at 22:59, Gerald Pfeifer wrote:
>
> I noticed this section on "Backwards Compatibility" in the libstdc++
> docs that talks about
>
> - glibc 2.0.x
> - GCC 3.2 (August 2002)
> - GCC 4.1 (February 2006)
>
> and links to "Migrating to GCC 4.1" and "Migration guide for GCC-3.2"
> documents.
>
> Does this still make sense (and serve real users or developers) or
> should this be trimmed quite a bit?
Yeah, that (and a lot more) should be trimmed from the libstdc++
manual. It's just time consuming to do it.
next prev parent reply other threads:[~2021-04-13 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 22:57 libstdc++-v3/doc/xml/manual/backwards_compatibility.xml Gerald Pfeifer
2021-04-13 15:19 ` Jonathan Wakely [this message]
2021-04-13 15:37 ` libstdc++-v3/doc/xml/manual/backwards_compatibility.xml Jonathan Wakely
2021-04-13 15:37 ` libstdc++-v3/doc/xml/manual/backwards_compatibility.xml 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='CAH6eHdSOzMzcx_Xsx3g8X4-0cNNaA018dEtxWxghh88M+_=6Fw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).