From: Ian Lance Taylor <iant@google.com>
To: Douglas B Rupp <rupp@gnat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: New port IA64 VMS and updated Alpha/VMS
Date: Tue, 21 Jul 2009 16:29:00 -0000 [thread overview]
Message-ID: <m3eisadmoe.fsf@google.com> (raw)
In-Reply-To: <4A65E876.2010409@gnat.com> (Douglas B. Rupp's message of "Tue\, 21 Jul 2009 09\:10\:30 -0700")
Douglas B Rupp <rupp@gnat.com> writes:
> 1) submit the target independent bits and pieces first then the
> configure bits.
This seems like the right approach to me.
Ian
prev parent reply other threads:[~2009-07-21 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 16:11 Douglas B Rupp
2009-07-21 16:29 ` Ian Lance Taylor [this message]
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=m3eisadmoe.fsf@google.com \
--to=iant@google.com \
--cc=gcc@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).