From: Jon Grant <jg@jguk.org>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Andrew Pinski <pinskia@gmail.com>,
gcc@gcc.gnu.org, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: onlinedocs formated text too small to read
Date: Thu, 06 Oct 2011 22:54:00 -0000 [thread overview]
Message-ID: <4E8E26C6.4020409@jguk.org> (raw)
In-Reply-To: <4E366697.6050003@gjlay.de>
Georg-Johann Lay wrote, On 01/08/11 09:40:
> Jon Grant wrote:
[.]
> http://gcc.gnu.org/ml/gcc/2011-07/msg00106.html
>
> CCed Gerald, I think he cares for that kind of things.
>
> If he does not answer (it's vacation time) file a PR so that it won't be forgotten.
>
> Johann
Thank you. I filled a PR now:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50642
Best regards, Jon
next prev parent reply other threads:[~2011-10-06 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 17:51 Jon Grant
2011-07-08 17:54 ` Andrew Pinski
2011-07-08 18:03 ` Paul Koning
2011-07-08 18:08 ` Georg-Johann Lay
[not found] ` <4E35E334.1030804@jguk.org>
2011-08-01 8:41 ` Georg-Johann Lay
2011-10-06 22:54 ` Jon Grant [this message]
2016-09-04 20:58 ` Gerald Pfeifer
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=4E8E26C6.4020409@jguk.org \
--to=jg@jguk.org \
--cc=avr@gjlay.de \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=pinskia@gmail.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).