From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: joseph@codesourcery.com
Cc: gcc-patches@gcc.gnu.org, pinskia@gmail.com,
tneumann@users.sourceforge.net
Subject: Re: [PATCH] compiling gcc with a C++ compiler 4/n
Date: Tue, 15 May 2007 15:28:00 -0000 [thread overview]
Message-ID: <10705151530.AA27461@vlsi1.ultra.nyu.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0705151148390.21854@digraph.polyomino.org.uk>
> I should point out that for this sort of thing the GNU Coding Standards
> allow you to say "All callers changed." rather than enumerating the
> callers individually. (I think it may still be useful to list the files
> changed, but not the functions within them - "* a.c, b.c, c.c: All callers
> changed.".)
I would definitely recommend listing the files, but I agree that the above
is enough for mechanical edits such as this.
prev parent reply other threads:[~2007-05-15 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 7:19 Thomas Neumann
2007-05-15 7:30 ` Andrew Pinski
2007-05-15 7:46 ` Thomas Neumann
2007-05-15 8:05 ` Andrew Pinski
2007-05-15 10:39 ` Thomas Neumann
2007-05-19 13:33 ` Gerald Pfeifer
2007-05-15 11:50 ` Joseph S. Myers
2007-05-15 15:28 ` Richard Kenner [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=10705151530.AA27461@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=pinskia@gmail.com \
--cc=tneumann@users.sourceforge.net \
/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).