Re: *** empty log message *** is a no-no

[Alexandre Oliva <oliva@lsd.ic.unicamp.br>]

On Nov 12, 1999, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:

> Thanks; this is just what I need, I think.  (*reads code*)  Hm, this
> doesn't pick out the bits of the changed ChangeLog that applies to
> different files if there's more than one file that's changed, does it?

It picks all of the checked-out ChangeLog that's not in the committed
ChangeLog.  And it will warn you if there are blank lines in that
portion, because this means you're checking in multiple unrelated
changes as a single commit, which is not good practice if you happen
to have to hunt for a particular change in the CVS logs.  But the
script will commit it, anyway.

It might be better for the CVS logs and for whoever wants to extract a
single patch from the CVS tree to commit every time you make a change
and test it.

> So I either want something that picks out the relevant bits from the
> ChangeLog entries I've added in 1), or some other way of doing
> things so that the ChangeLog will be generated in 5).

I believe this script should do it.  If it doesn't, please let me
know, I may be able to tweak it to fit your needs.

-- 
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them