public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@windriver.com>
To: mark@codesourcery.com, pfeifer@dbai.tuwien.ac.at
Cc: aoliva@redhat.com, gcc@gcc.gnu.org, hzoli@austin.ibm.com
Subject: Re: ChangeLog entries (was: C++ codegen bug for switch statement(s))
Date: Wed, 13 Sep 2000 17:28:00 -0000	[thread overview]
Message-ID: <200009140028.RAA02299@kankakee.wrs.com> (raw)

> Date: Thu, 14 Sep 2000 00:54:36 +0200 (CEST)
> From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>

> On Wed, 13 Sep 2000, Mark Mitchell wrote:
> > I don't generally make testsuite ChangeLog entries.  Is that something
> > we're supposed to do?

> Well, I don't know! ;-)  But once I do, I'll update the web page,
> promised.

I don't see enough value in it when measured against the cost.  In a
well done testcase, there are very few edits required post writing it,
there usually aren't interactions with other files, the comment is
usually something like, {Added.,Removed.,Fixed.} lending little
additional information.  ChangeLogs predate things like public
anonymous cvs repositories.  One might say that the ChangeLog
mostly replicates the cvs log.

I'd say, let's mandate changelog entries for any framework fixes
(lib/*, g++.other/*.exp), let's skip entries that would just say,
added, and leave the remainder up to the person doing the work.


Now, if enough other people do see a value in doing it, we can do it,
I don't think it is all that much extra work.  Out of curiosity, has
anybody made use of what changelogs are there today?

             reply	other threads:[~2000-09-13 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-13 17:28 Mike Stump [this message]
2000-09-13 18:20 ` ChangeLog entries (was: C++ codegen bug for switchstatement(s)) Mark Mitchell
2000-09-13 19:53   ` ChangeLog entries (was: C++ codegen bug for switch statement(s)) Michael Meissner
2000-09-13 22:41     ` ChangeLog entries (was: C++ codegen bug for switchstatement(s)) Mark Mitchell
     [not found] <20000913153823P.mitchell@codesourcery.com>
2000-09-13 15:54 ` ChangeLog entries (was: C++ codegen bug for switch statement(s)) Gerald Pfeifer
2000-09-13 16:26   ` Jeffrey A Law

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=200009140028.RAA02299@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hzoli@austin.ibm.com \
    --cc=mark@codesourcery.com \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).