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

[Jan Vroonhof <vroonhof@math.ethz.ch>]

Denys Duchier <Denys.Duchier@ps.uni-sb.de> writes:

> Yes, that's a nice feature.  However, the ChangeLog idea is not really
> appropriate for concurrent development (the record of changes only
> becomes meaningful when it is synchronized with the repository,
> i.e. at commit points).

No they are very useful for concurrent development. However I think
you mean concurrent development where everybody commits often.
I am thinking of shared development over the internet where typically
one commits complete bits of work. If they than also first submitted
for general review in the form of Patches, changelogs come in very handy. 

> `C-x v =' to diff with the committed version.  Then I document the
> changes in fairly free format.  Typically, I have also added comments
> in the file documenting the new stuff, or making clear the invariants
> that should not be violated, etc... I also include these comments in
> the log entry.

I like the fact that ChangeLog entries have a strict format that
includes the function names. I use them as a kind of CVS
annotate that is function based and not line based.
In addition in shared internet project you have the problem that CVS
annotate does not work over anonymous CVS.

> > Is the resolution on the time stamps that important?

In internet based collaborative effort timescales are of the order of
days anyway, so the resolution of one day is sufficient.

Jan