Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-18 00:33:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

maint: prefer "commit message" to "log entry".

Browse Source 
* README-hacking: here.
Suggested by Stefano Lattarini.
This commit is contained in:
Akim Demaille
2012-05-08 12:06:49 +02:00
parent 0b7fba1335
commit 7de42e52bf
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README-hacking
View File

@@ -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 the appropriate paperwork. Second, be sure to add their name and
email address to THANKS. 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 ** 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. 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 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 The version number, *and* the date of the release (including for
betas). 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.'. Should have an entry similar to `Version 2.3b.'.
** Tag the release ** Tag the release
@@ -251,7 +251,7 @@ similar to:
git tag -a v2.3b git tag -a v2.3b
The log message can be simply: The commit message can be simply:
Bison 2.3b Bison 2.3b