From: Alan Modra <amodra@bigpond.net.au>
To: Nick Clifton <nickc@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: Patches to move cgen files to C90 with prototypes
Date: Sat, 09 Aug 2003 00:48:00 -0000 [thread overview]
Message-ID: <20030808130731.GQ27145@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <m3k79o9uz4.fsf@redhat.com>
On Fri, Aug 08, 2003 at 01:47:43PM +0100, Nick Clifton wrote:
> Hi Frank,
>
> > Given that such mechanical conversions end up being done en-masse for
> > all the functions in a given file, anyone wanting to know those things
> > could find the single line
> > * file.c: c90-ized.
> > and understand.
>
> Yes that would be fair.
>
> Let me put it this way. I am not going to reject reformatting patches
> just because the ChangeLog entry does not mention every function by
> name. If the submitter has gone to the trouble of naming the
> functions then that is great, but I am not going to insist on it.
Oh good. I was going to mention the other downside to insisting on
per-function ChangeLog entries for C90 conversions is that patches might
not be submitted..
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2003-08-08 13:07 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
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 [this message]
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=20030808130731.GQ27145@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@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).