public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François Dumont" <frs.dumont@gmail.com>
To: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 107189 Remove useless _Alloc_node
Date: Mon, 14 Nov 2022 18:56:03 +0100	[thread overview]
Message-ID: <7a266d31-cf97-6143-d930-6020bc4ed102@gmail.com> (raw)
In-Reply-To: <8266b5be-256c-4be2-84db-3a880e849d41@gmail.com>

Gentle reminder.

Sorry if I should have committed it as trivial but I cannot do it 
anymore now that I asked :-)


On 12/10/22 22:18, François Dumont wrote:
> libstdc++: Remove _Alloc_node instance in _Rb_tree [PR107189]
>
>     libstdc++-v3/ChangeLog:
>
>             PR libstdc++/107189
>             * include/bits/stl_tree.h 
> (_Rb_tree<>::_M_insert_range_equal): Remove
>             unused _Alloc_node instance.
>
> Ok to commit ?
>
> François



  reply	other threads:[~2022-11-14 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 20:18 François Dumont
2022-11-14 17:56 ` François Dumont [this message]
2023-01-04 21:13   ` François Dumont
2023-01-12 12:01     ` Jonathan Wakely
2023-01-12 12:02       ` 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=7a266d31-cf97-6143-d930-6020bc4ed102@gmail.com \
    --to=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).