From: Bruce Korb <bkorb@gnu.org>
To: Jonathan Wakely <jwakely@redhat.com>, Jonas Jelten <jj@sft.mx>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] fixincludes breaks mingw64 build
Date: Tue, 11 Jun 2019 20:38:00 -0000 [thread overview]
Message-ID: <84efaa72-7093-d652-fd65-99dd5a9c3e45@gnu.org> (raw)
In-Reply-To: <20190531191556.GA2599@redhat.com>
On 5/31/19 12:15 PM, Jonathan Wakely wrote:
>> Alright, thanks for the hint. I was just following the instructions in
>> gcc-9.1.0/fixincludes/README:
>>
>> """
>> Please also send relevant information to gcc-bugs@gcc.gnu.org,
>> gcc-patches@gcc.gnu.org and,
>> please, to me: bkorb@gnu.org.
>> """
>
> Oh, indeed!
> Bruce, should that suggest submitting something to Bugzilla instead?
> Mails sent directly to gcc-bugs tend to get lost among all the
> automated email from Bugzilla.
Looks like old stuff that wasn't updated. I'd copied that text from
other sources and seems out of date.
I should probably update the e-address as well. Yes, I still receive
gnu.org email, but not daily. As infrequent as monthly. Can I do
something to auto-forward it to an e-address I process daily?
Finally, my gcc sources are also years out of date, so if someone is
willing to tweak the docs for me, it'd save some bother. :) I'm actually
retired now and spend more time with a camera than with code.
Cheers - Bruce
next prev parent reply other threads:[~2019-06-11 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 13:59 Jonas Jelten
2019-05-31 14:51 ` Jonathan Wakely
2019-05-31 15:35 ` Jonas Jelten
2019-05-31 19:48 ` Jonathan Wakely
2019-06-11 20:38 ` Bruce Korb [this message]
2019-08-12 22:09 ` Gerald Pfeifer
2019-06-11 20:32 ` Bruce Korb
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=84efaa72-7093-d652-fd65-99dd5a9c3e45@gnu.org \
--to=bkorb@gnu.org \
--cc=bruce.korb+gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jj@sft.mx \
--cc=jwakely@redhat.com \
/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).