public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: Patches to move cgen files to C90 with prototypes
Date: Fri, 08 Aug 2003 12:54:00 -0000	[thread overview]
Message-ID: <20030808121529.GB27175@redhat.com> (raw)
In-Reply-To: <m38yq4bck9.fsf@redhat.com>

Hi -


On Fri, Aug 08, 2003 at 12:42:30PM +0100, Nick Clifton wrote:
> [...]
> > Do you reckon anyone is going to be interested in something as
> > trivial as a conversion to C90?
> 
> Yes.  The conversion might possibly introduce a bug.  Or someone might
> want to get hold of the latest version of the function prior to its
> conversion to C90.  

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.

Would you be of the same opinion if someone checked in, say, code
that's reformatted with the most fashionable indent settings?


> Or, there could be any number of reasons.

Perhaps.


> Including the function names in the ChangeLog entry when doing these
> conversions is tedious but it is not that hard to do so I think that
> it is worthwhile.

On the downside, it renders the ChangeLog so tediously verbose that
manual browsing is frustrated.  People not only search through ChangeLog
files for functions of interest.  They sometimes want to scan it top
to bottom.


- FChE

  reply	other threads:[~2003-08-08 12:15 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 [this message]
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=20030808121529.GB27175@redhat.com \
    --to=fche@redhat.com \
    --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).