Le 8 mai 2012 à 11:43, Stefano Lattarini a écrit : > Hi Akim. > > On 05/08/2012 10:37 AM, Akim Demaille wrote: >> >> -** If a change fixes a test, mention the test in the ChangeLog entry. >> +** If a change fixes a test, mention the test in the log entry. >> > Maybe /log entry/commit message/? It is much clearer IMHO. > > Similarly for other usages throughout the patch.
hi Stefano, Why not, indeed. I installed this. From 7de42e52bfad5af2dbf15a05909e8734e468580c Mon Sep 17 00:00:00 2001 From: Akim Demaille <[email protected]> Date: Tue, 8 May 2012 12:06:49 +0200 Subject: [PATCH 1/3] maint: prefer "commit message" to "log entry". * README-hacking: here. Suggested by Stefano Lattarini. --- README-hacking | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README-hacking b/README-hacking index e481da7..70f346a 100644 --- a/README-hacking +++ b/README-hacking @@ -15,10 +15,10 @@ First, if it is a large change, you must make sure they have signed the appropriate paperwork. Second, be sure to add their name and email address to THANKS. -** If a change fixes a test, mention the test in the log entry. +** If a change fixes a test, mention the test in the commit message. ** Bug reports -If somebody reports a new bug, mention his name in the log entry +If somebody reports a new bug, mention his name in the commit message and in the test case you write. Put him into THANKS. The correct response to most actual bugs is to write a new test case @@ -241,7 +241,7 @@ occurrences of PACKAGE_COPYRIGHT_YEAR in configure.ac. The version number, *and* the date of the release (including for betas). -** Mention the release name in a commit log +** Mention the release name in a commit message Should have an entry similar to `Version 2.3b.'. ** Tag the release @@ -251,7 +251,7 @@ similar to: git tag -a v2.3b -The log message can be simply: +The commit message can be simply: Bison 2.3b -- 1.7.10.1
