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

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:

> If you don't mind using a script to commit your stuff, use this one:

[...]

> # The commit message will be extracted from the differences between
> # the local ChangeLog and the one in the repository (unless a message
> # was specified with `-m' or `-F').

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?

This is how I work:

1a) I read a bunch of bug reports, and I fix a bunch of bugs in a bunch
    of files, noting everything in the ChangeLog.
1b) I fix a bunch more bugs.

2) I see that it doesn't compile, so I fix a bunch more.

3) I see that it compiles, so I start it.

4) I see that it didn't start, so I go back to 1b) a couple of times

5) I say "cvs commit -m ''", which is why you get all those empty
   log messages.

I don't really want to commit before after I've done 4).  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).

Shirley this can't be an unusual way of working?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen