From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,254d058bd7de11b3
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!proxad.net!newsfeed.stueberl.de!feed.news.tiscali.de!news.belwue.de!LF.net!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: Writing changelog entries
Date: Wed, 05 Jan 2005 01:47:11 +0100
Message-ID: <87wtus3do0.fsf@deneb.enyo.de>
References: <87y8f96imj.fsf@deneb.enyo.de>
	<mailman.27.1104884920.527.comp.lang.ada@ada-france.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: albireo.enyo.de 1104886033 30732 212.9.189.171 (5 Jan 2005 00:47:13
 GMT)
X-Complaints-To: 
Cancel-Lock: sha1:mpEGH0Y2wpEBx2D5g/1CVQZlyVs=
Xref: g2news1.google.com comp.lang.ada:7454
Date: 2005-01-05T01:47:11+01:00
List-Id: <comp.lang.ada>

* Stephen Leake:

> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> How are you writing your changelog entries?
>
> This is probably highly project specific, but I'll give you what I do.
>
> I just use Emacs and CVS, and then when I do a release, I use
> cvs2cl.pl (http://www.red-bean.com/cvs2cl/) to generate a changelog.

Generating the changelog is not the problem.  It's the format of the
entries in it.  Many projects have explicit guidelines which ensure
that you can grep the changelog and find the change which affected a
particular entity.  However, these guidelines are C-specific and do
not take homographs into account (and neither nested subprograms, and
so on).