public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Update incorrect statement about mainline in docs
Date: Tue, 19 Apr 2022 11:40:10 +0100	[thread overview]
Message-ID: <CACb0b4nrxPhTQo00axN+=NvTGaF9gLk5A437afrMghV+6JPmpA@mail.gmail.com> (raw)
In-Reply-To: <39rr4991-5317-7p7s-3n7n-14rp26p1o4o8@fhfr.qr>

On Tue, 19 Apr 2022 at 08:01, Richard Biener <rguenther@suse.de> wrote:
>
> On Thu, 14 Apr 2022, Jonathan Wakely wrote:
>
> > On Thu, 14 Apr 2022 at 11:55, Richard Biener <rguenther@suse.de> wrote:
> > >
> > > On Thu, 14 Apr 2022, Jonathan Wakely wrote:
> > >
> > > > On Thu, 14 Apr 2022 at 11:36, Richard Biener <rguenther@suse.de> wrote:
> > > > >
> > > > > On Thu, 14 Apr 2022, Jonathan Wakely wrote:
> > > > >
> > > > > > This fixes some misleading text in the libstdc++ manual that says the
> > > > > > docs for the gcc-11 branch refer to mainline.
> > > > > >
> > > > > > Richi, is this OK for the gcc-11 branch now? It's been wrong for 11.1
> > > > > > and 11.2, but it would still be nice to fix.
> > > > >
> > > > > Yes, it's OK.  I notice the same problem exists on the GCC 10 branch
> > > > > but GCC 9 at least mentions GCC 9 once ;)
> > > >
> > > > Yes, I fixed it for gcc-9.3.0, but forgot to do it for gcc-10 and gcc-11.
> > > >
> > > > I pushed r10-10534 to fix gcc-10 (since that's open for doc changes)
> > > > and have now pushed r11-9881
> > > > as well.
> > > >
> > > > Maybe this year I'll remember to do it for gcc-12 after we branch from trunk!
> > >
> > > Add an entry to branching.html!
> >
> > Like this? OK for wwwdocs?
>
> Maybe
>
> "Notify libstdc++ maintainers to update ..."
>
> ?
>
> OK with that change.

Yes, that's better. Pushed with that change, thanks.


      reply	other threads:[~2022-04-19 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 10:29 Jonathan Wakely
2022-04-14 10:36 ` Richard Biener
2022-04-14 10:44   ` Jonathan Wakely
2022-04-14 10:55     ` Richard Biener
2022-04-14 16:09       ` Jonathan Wakely
2022-04-19  7:01         ` Richard Biener
2022-04-19 10:40           ` 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='CACb0b4nrxPhTQo00axN+=NvTGaF9gLk5A437afrMghV+6JPmpA@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).