From: Gerald Pfeifer <gerald@pfeifer.com>
To: Douglas Rupp <rupp@gnat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Un-obsolete Interix
Date: Fri, 08 Jul 2011 11:25:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1107081235340.30592@gerinyyl.fvgr> (raw)
In-Reply-To: <4E0B3D67.7040109@gnat.com>
Hi Doug,
On Wed, 29 Jun 2011, Douglas Rupp wrote:
> An update to the IA-32/x86-64 section seems the right place. I confess
> to being ignorant about how to update this html page. Please advise.
at http://gcc.gnu.org/cvs.html I tried to summarize things a bit.
If you have any questions, don't hesitate to let me know!
If things turn out to be tricky, you're also very welcome to download
the current page using a browser, just send me a diff, and I'll take
care of the rest.
Gerald
next prev parent reply other threads:[~2011-07-08 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 16:06 Douglas Rupp
2011-07-08 11:25 ` Gerald Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 17:35 Douglas B Rupp
2011-06-09 19:13 ` Joseph S. Myers
2011-06-09 19:32 ` Douglas B Rupp
2011-06-12 13:50 ` 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=alpine.LNX.2.00.1107081235340.30592@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rupp@gnat.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).