diff options
| author | Daiki Ueno <ueno@gnu.org> | 2015-10-14 10:20:34 +0900 |
|---|---|---|
| committer | Daiki Ueno <ueno@gnu.org> | 2015-10-14 15:00:09 +0900 |
| commit | 614ff78da50d3b16b538c07d338dc4a9b32d6261 (patch) | |
| tree | f83f25d6bb018d560ad99ecb95b767ee90b79881 /HACKING | |
| parent | ac1632889dfc001ca13a4debaf1e632889d866d0 (diff) | |
| download | external_gettext-614ff78da50d3b16b538c07d338dc4a9b32d6261.zip external_gettext-614ff78da50d3b16b538c07d338dc4a9b32d6261.tar.gz external_gettext-614ff78da50d3b16b538c07d338dc4a9b32d6261.tar.bz2 | |
build: Remove ChangeLogs
Generate ChangeLog files at "make dist" time, using
gitlog-to-changelog. We still keep ChangeLog files under "po" and
"intl" directories, since those files are copied as part of gettext
infrastructure and it is still meaningful to have them there.
* .gitignore: Add ChangeLog files.
* Admin/release-steps: Remove mention of running update-changelog
script.
* Admin/update-changelog: Remove.
* Makefile.am (gen-ChangeLog): New rule.
* autogen.sh: Copy gitlog-to-changelog from gnulib. Create empty
ChangeLog files to suppress Automake errors.
* gettext-tools/doc/Makefile.am (EXTRA_DIST): Remove ChangeLog.0.
* gettext-tools/man/Makefile.am (EXTRA_DIST): Remove ChangeLog.0.
* gettext-tools/src/Makefile.am (EXTRA_DIST): Remove ChangeLog.0.
* gettext-tools/tests/Makefile.am (EXTRA_DIST): Remove ChangeLog.0.
* gnulib-local/Makefile.am (EXTRA_DIST): Remove ChangeLog files.
* */ChangeLog: Rename to ChangeLog.0 or ChangeLog.1.
* HACKING: Add brief guideline to submit patches.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 21 |
1 files changed, 21 insertions, 0 deletions
@@ -73,3 +73,24 @@ After fetching the sources from the repository, peek at the comments in autogen.sh, then run "./autogen.sh"; then you can proceed with "./configure" as usual. +Submitting patches +================== + +Patches should be sent to bug-gettext@gnu.org, the bug/feature mailing +list. You can subscribe to the mailing list, or see the list +archives, by following links from +http://savannah.gnu.org/mail/?group=gettext . + +To email a patch you can use a shell command like 'git format-patch +-1' to create a file, and then attach the file to your email. + +GNU gettext development no longer stores descriptions of new changes +in ChangeLog files. Instead, a single ChangeLog file is generated +from the commit messages when a release is prepared. So changes you +commit should not touch any of the ChangeLog files in the repository, +but instead should contain the log entries in the commit message. + +For the style of a ChangeLog entry, see the "Change Logs" section of +the GNU coding standards: + + http://www.gnu.org/prep/standards/html_node/Change-Logs.html |