summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@lorry>2015-12-28 00:06:36 +0000
committerLorry Tar Creator <lorry-tar-importer@lorry>2015-12-28 00:06:36 +0000
commit6eb5949dd99d174393465069c2fd0bab32deddcc (patch)
treed104f72ac2dcb0f592b1c8e06a5af6790bd4080c /HACKING
parent482840e61f86ca321838a91e902c41d40c098bbb (diff)
downloadgettext-tarball-6eb5949dd99d174393465069c2fd0bab32deddcc.tar.gz
gettext-0.19.7gettext-0.19.7
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING21
1 files changed, 21 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 6e94e3f..505a16d 100644
--- a/HACKING
+++ b/HACKING
@@ -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