public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Michael Meissner <bin-mail@the-meissners.org>
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com, nickc@redhat.com
Subject: Patches to move cgen files to C90 with prototypes
Date: Thu, 07 Aug 2003 00:44:00 -0000	[thread overview]
Message-ID: <16177.39941.684697.94934@casey.transmeta.com> (raw)
In-Reply-To: <20030807001021.GA31218@tiktok.the-meissners.org>

Michael Meissner writes:
 > 2003-08-06  Michael Meissner  <gnu@the-meissners.org>
 > 
 >      ... massively large changelog entry,
 >      ... especially for just a k&r -> c90 substitution

fwiw, I think people think they're under far too much pressure to
write anally correct changelog entries before a patch will get accepted.

Nick, in this particular case, does one really have to mention every function?
How about this instead?

2003-08-06  Michael Meissner  <gnu@the-meissners.org>

	* cgen-dis.in (*): Remove PARAMS macro.  Use void * instead of PTR.
	* cgen-ibld.in (*): Ditto.
	* cgen-asm.in (*): Ditto.
	* cgen-dis.c (*): Ditto.
	* cgen-opc.c (*): Ditto.
	* cgen-asm.c (*): Ditto.

[N.B. I said "in this particular case".  Don't try to generalize
my comments too far ...]

  reply	other threads:[~2003-08-07  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  0:23 Michael Meissner
2003-08-07  0:44 ` Doug Evans [this message]
2003-08-07 13:52   ` Michael Meissner
2003-08-08  8:18     ` Nick Clifton
2003-08-08 11:49       ` Alan Modra
2003-08-08 12:15         ` Nick Clifton
2003-08-08 12:54           ` Frank Ch. Eigler
2003-08-08 13:07             ` Nick Clifton
2003-08-09  0:48               ` Alan Modra
2003-08-08  9:27 ` Nick Clifton

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=16177.39941.684697.94934@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=bin-mail@the-meissners.org \
    --cc=binutils@sources.redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=nickc@redhat.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).