On Wed, 10 Jan 2024 at 23:31, Jonathan Wakely <jwak...@redhat.com> wrote: > > On Wed, 10 Jan 2024 at 21:28, Michael Levine (BLOOMBERG/ 120 PARK) > <mlevin...@bloomberg.net> wrote: > > > > From a67cfd07ce27a62f764b381268502acb68b6bad9 Mon Sep 17 00:00:00 2001 > > From: Michael Levine <mlevin...@bloomberg.net> > > Date: Wed, 10 Jan 2024 15:48:46 -0500 > > Subject: [PATCH 1/2] Removed a duplicate define directive for > > __glibcxx_want_ranges_iota > > > > Signed-off-by: Michael Levine <mlevin...@bloomberg.net> > > --- > > libstdc++-v3/include/std/ranges | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/libstdc++-v3/include/std/ranges > > b/libstdc++-v3/include/std/ranges > > index 81a857502e3..ae857f8c7fc 100644 > > --- a/libstdc++-v3/include/std/ranges > > +++ b/libstdc++-v3/include/std/ranges > > @@ -59,7 +59,6 @@ > > #define __glibcxx_want_ranges_chunk_by > > #define __glibcxx_want_ranges_enumerate > > #define __glibcxx_want_ranges_iota > > -#define __glibcxx_want_ranges_iota > > #define __glibcxx_want_ranges_join_with > > #define __glibcxx_want_ranges_repeat > > #define __glibcxx_want_ranges_slide > > Thanks for the patch, this looks obviously correct. > > Please note that all patches need to go to the gcc-patches list (as > well as the more specific list, like this one, so e.g. add both to the > email's To: header, or CC one of them). > > Also please don't touch the ChangeLog file in patches. We have been > auto-generating the ChangeLog files nightly for some years now, so you > should not edit them manually (and including it in the patch just > means the patch won't apply cleanly after the next time the file is > regen'd). > > But I can take care of that and apply the patch, there's no need for a > corrected patch. Thanks again for the contribution.
Pushed to trunk now, thanks again.
