Update documentation with instructions for patch submission

* README.template: Add notes on how to submit patches.
* README.git: Point to the README.
* doc/make.texi: Ditto.

diff --git a/README.git b/README.git
index 1081e295c762b2739a666a758a522b619b75ed89..1f01ce18d92349a0c75dc09f862ac5dd68d7ffcf 100644 (file)
--- a/README.git
+++ b/README.git
@@ -31,8 +31,11 @@ make source code via Git from the FSF's Savannah project
 Changes using Git
 -----------------
 
-For non-developers, you can continue to provide patches as before, or if you
-make a public repository I can pull from that if you prefer.
+If you do not have push privileges to the GNU make Git repository, see the
+README file section "Submitting Patches" for information.
+
+If you have push privileges to the GNU make Git repository keep this
+information in mind:
 
 Starting with GNU make 4.0 we no longer keep a separate ChangeLog file in
 source control.  We use the Gnulib git-to-changelog conversion script to

diff --git a/README.template b/README.template
index e282fd0d0311f93ca6a8cc29a181defc9e1704f6..215d749c61f4a2294e4df5c05aaf0482ea2373a5 100644 (file)
--- a/README.template
+++ b/README.template
@@ -86,6 +86,27 @@ If you need help using GNU make, try these forums:
   news:gnu.utils.bug
 
 
+Submitting Patches
+------------------
+
+If you'd like to propose a patch for changes to GNU make, you should create a
+patch with your changes.  If you're making your changes in a Git workspace you
+can run "git format-patch" to create a patch file.  If not, you can use the
+patch(1) utility.
+
+Once you have a patch you can submit it in any of these ways:
+
+  * Create a bug on Savannah and add the patch as an attachment:
+      https://savannah.gnu.org/bugs/?group=make&func=additem
+
+  * Send the patch via email to <bug-make@gnu.org>: be sure to add it as an
+    attachment to avoid interference by email processors.
+
+Be aware that all non-trivial changes proposed for GNU make require FSF
+copyright paperwork to be completed before they can be accepted.  Contact
+<bug-make@gnu.org> for help.
+
+
 Git Access
 ----------
 

diff --git a/doc/make.texi b/doc/make.texi
index 52d727128c235c45dea54ab1332d2c7e6aa1abdc..e555373a2f579514c29fc728352394452871332c 100644 (file)
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -511,6 +511,9 @@ include the type of machine and operating system you are using.  One
 way to obtain this information is by looking at the final lines of
 output from the command @samp{make --help}.
 
+If you have a code change you'd like to submit, see the @file{README} file
+section ``Submitting Patches'' for information.
+
 @node Introduction, Makefiles, Overview, Top
 @comment  node-name,  next,  previous,  up
 @chapter An Introduction to Makefiles