Unuseful commit message

Unuseful commit message

[Eli Zaretskii]

This commit message is not useful at all:

    revno: 103418
    committer: Paul Eggert <eggert@cs.ucla.edu>
    branch nick: trunk
    timestamp: Fri 2011-02-25 07:23:41 +0000
    message:
      Regenerate.

One needs to use "bzr log --verbose" or "bzr diff" to see which files
were regenerated.  It would also be good to have the reason(s) for
regeneration in the log message (or at least in ChangeLog).

Re: Unuseful commit message

[Paul Eggert]

On 02/25/2011 01:05 AM, Eli Zaretskii wrote:
> It would also be good to have the reason(s) for
> regeneration in the log message (or at least in ChangeLog).

OK, I added the following:

=== modified file 'ChangeLog'
--- ChangeLog	2011-02-25 07:23:41 +0000
+++ ChangeLog	2011-02-25 10:02:17 +0000
@@ -1,7 +1,8 @@
 2011-02-25  Paul Eggert  <eggert@cs.ucla.edu>
 
 	* configure, lib/Makefile.in, lib/getopt_int.h, lib/gnulib.mk:
-	* lib/stdlib.in.h, m4/stdlib_h.m4: Regenerate.
+	* lib/stdlib.in.h, m4/stdlib_h.m4: Regenerate to incorporate
+	recent changes to configure.in and to gnulib.
 
 2011-02-24  Glenn Morris  <rgm@gnu.org>
 

Re: Unuseful commit message

[Eli Zaretskii]

> Date: Fri, 25 Feb 2011 02:21:43 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
> 
> On 02/25/2011 01:05 AM, Eli Zaretskii wrote:
> > It would also be good to have the reason(s) for
> > regeneration in the log message (or at least in ChangeLog).
> 
> OK, I added the following:

Thank you.

Re: Unuseful commit message

[Glenn Morris]

Eli Zaretskii wrote:

> One needs to use "bzr log --verbose" or "bzr diff" to see which files
> were regenerated.  It would also be good to have the reason(s) for
> regeneration in the log message (or at least in ChangeLog).

wrt ChangeLogs, rms said "There is no need to indicate regeneration of
files such as configure in ChangeLog." This is documented in
admin/notes/changelogs. (FWIW, personally I agree with him.)