From 3efba8a1452c92ac474f3c08ac40ed45af4c67f9 Mon Sep 17 00:00:00 2001 From: Paul Smith Date: Sat, 18 Dec 2021 18:25:38 -0500 Subject: [PATCH] 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. --- README.git | 7 +++++-- README.template | 21 +++++++++++++++++++++ doc/make.texi | 3 +++ 3 files changed, 29 insertions(+), 2 deletions(-) diff --git a/README.git b/README.git index 1081e295..1f01ce18 100644 --- 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 e282fd0d..215d749c 100644 --- 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 : 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 + for help. + + Git Access ---------- diff --git a/doc/make.texi b/doc/make.texi index 52d72712..e555373a 100644 --- 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