From: Jonathan Wakely <jwakely@redhat.com>
To: Felipe Magno de Almeida <felipe.m.almeida@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Fix compilation errors with libstdc++v3 for AVR target and allow --enable-libstdcxx
Date: Sat, 12 Nov 2016 03:19:00 -0000 [thread overview]
Message-ID: <20161112031942.GC21992@redhat.com> (raw)
In-Reply-To: <CADfx-VSUVCZ2k01OpZ-4vD3kL++xAmRz1P7m3CgRGbwW_Ojv8Q@mail.gmail.com>
On 10/11/16 13:39 -0200, Felipe Magno de Almeida wrote:
>Hello,
>
>Sorry for top-posting, but this is a ping for the attached patch.
>
>The patch doesn't seem to have been applied nor refused. So I'm
>pinging to see if I need to change something? I already have a
>copyright assignment now.
Sorry for the delay. It's on my list to deal with. I've been on
vacation and then busy at C++ standards meeting.
>I'm attaching a updated patch that doesn't conflict in the Changelog
>file.
Don't include ChangeLogs in the patch, just include the ChangeLog
content in the email, so there's no problem with the ChangeLog churn
making the patch fail :-)
I'll deal with it next week when I'm back home.
next prev parent reply other threads:[~2016-11-12 3:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 5:10 Felipe Magno de Almeida
2016-09-16 5:53 ` Marc Glisse
2016-09-16 6:19 ` Felipe Magno de Almeida
2016-09-16 7:01 ` Felipe Magno de Almeida
2016-11-10 15:40 ` Felipe Magno de Almeida
2016-11-10 15:52 ` Felipe Magno de Almeida
2016-12-06 15:08 ` Jonathan Wakely
2016-12-06 17:59 ` Jonathan Wakely
2023-09-29 14:07 ` Jonathan Wakely
2023-09-29 14:30 ` Jonathan Wakely
2016-12-06 18:11 ` Jonathan Wakely
2016-11-12 3:19 ` Jonathan Wakely [this message]
2016-12-06 18:45 ` Jonathan Wakely
2016-12-14 21:43 ` Felipe Magno de Almeida
2016-12-15 11:34 ` Jonathan Wakely
[not found] ` <CADfx-VRosQDhU0uOQhknAzcbhVyrdnQ9n=9NmGVmPkP9n+NqGg@mail.gmail.com>
2016-12-16 12:51 ` Jonathan Wakely
2016-12-23 16:09 ` Felipe Magno de Almeida
2017-01-10 14:16 ` 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=20161112031942.GC21992@redhat.com \
--to=jwakely@redhat.com \
--cc=felipe.m.almeida@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).