From: Ian Lance Taylor <ian@airs.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Move option-related hooks to common structure
Date: Sat, 28 May 2011 05:16:00 -0000 [thread overview]
Message-ID: <m3ipsvepag.fsf@pepe.airs.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1105271611400.27055@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Fri, 27 May 2011 16:13:16 +0000 (UTC)")
"Joseph S. Myers" <joseph@codesourcery.com> writes:
> Ian, what is the right way to handle the gofrontend change in this
> patch (to update code for the move of a hook from targetm to
> targetm_common)? It's small, mechanical and I think below the
> threshold of significance for copyright.
I agree, but to avoid any confusion I just moved the code into the
gcc-specific area, as is appropriate in any case. Please move your
patch from go/gofrontend/export.cc to the identical code at the end of
go/go-backend.c.
Ian
next prev parent reply other threads:[~2011-05-27 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 17:44 Joseph S. Myers
2011-05-27 18:17 ` Paul Koning
2011-05-28 5:16 ` Ian Lance Taylor [this message]
2011-06-06 9:05 ` Ping " Joseph S. Myers
2011-06-14 17:33 ` Ian Lance Taylor
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=m3ipsvepag.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).