From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Matt Kraai <kraai@alumni.cmu.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: "obvious" requirements
Date: Mon, 19 May 2003 10:35:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305191119070.3171@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030518232511.GE13668@ftbfs.org>
On Sun, 18 May 2003, Matt Kraai wrote:
> I'd like to make a obvious fix to tree.c (i.e., remove a blank
> line). Should I add an entry to the ChangeLog and/or post the
> patch to gcc-patches?
ChangeLog? Dunno about such a corner case.
gcc-patches? Definitely, though it's fine after the fact for obvious
changes.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-19 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 0:38 Matt Kraai
2003-05-19 10:35 ` Gerald Pfeifer [this message]
2003-05-19 15:07 ` Matt Kraai
2003-05-20 12:01 ` Gerald Pfeifer
2003-05-20 14:12 ` Kelley Cook
2003-05-20 16:14 ` Andrew Haley
2003-05-20 16:43 ` Fergus Henderson
2003-05-20 17:56 ` Gerald Pfeifer
2003-05-20 22:58 Robert Dewar
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=Pine.BSF.4.55.0305191119070.3171@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=kraai@alumni.cmu.edu \
/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).