>From 502ace22e9af0c16020b2494af466cd83a40a92c Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Wed, 30 Dec 2015 13:14:57 +0100 Subject: [PATCH 1/3] doc: fix typos in README-hacking * README-hacking (Required format for check-in messages): s/maded/made/; s/modifies/modified/ --- README-hacking | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README-hacking b/README-hacking index 427f29c..1ec66f0 100644 --- a/README-hacking +++ b/README-hacking @@ -122,10 +122,10 @@ modifying the Texinfo source, use the section name. After the colon, describe the change you made to that function. If you made a related change mention the places you made that change, -too. If you maded many individually small changes, you can summarise +too. If you made many individually small changes, you can summarise these if they're not individually interesting. For example you could just say "Update all callers to remove this function argument". If -that change spans several files, mention the other files modifies. +that change spans several files, mention the other files modified. -- 2.1.4 >From 00311bb105c38fc0763d12c6fc18d74cc489d137 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Wed, 30 Dec 2015 13:15:57 +0100 Subject: [PATCH 2/3] doc: mention copyright assignment check prior to 'git push' * README-hacking (Required format for check-in messages): Add a paragraph aiming at maintainers to check that the author of the commit has proper copyright assignment in place, or otherwise how to document that this is not needed. --- README-hacking | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README-hacking b/README-hacking index 1ec66f0..d3ce176 100644 --- a/README-hacking +++ b/README-hacking @@ -127,6 +127,14 @@ these if they're not individually interesting. For example you could just say "Update all callers to remove this function argument". If that change spans several files, mention the other files modified. +Note for maintainers: +Prior to pushing a commit in the name of someone else to the public Git +repository, please check if that person has undergone the "Copyright +assignment" process for GNU findutils described below, or - in case of a +trivial (<10 lines) change - document that such paperwork is not required +by adding this line to the commit message: + + Copyright-paperwork-exempt: Yes Making commits locally -- 2.1.4 >From 20c7ebbccaf392cfba8f5e3aa9ef8040b24e6735 Mon Sep 17 00:00:00 2001 From: Bernhard Voelker Date: Wed, 30 Dec 2015 13:12:42 +0100 Subject: [PATCH 3/3] doc: mention 'make syntax-check' in README-hacking * README-hacking (Submitting patches): Add the above. --- README-hacking | 1 + 1 file changed, 1 insertion(+) diff --git a/README-hacking b/README-hacking index d3ce176..f5306c1 100644 --- a/README-hacking +++ b/README-hacking @@ -202,6 +202,7 @@ Here is a complete session emacs NEWS # make sure you didn't break anything + make syntax-check make distcheck # commit the change and send the patches. -- 2.1.4