gbranden pushed a commit to branch master
in repository groff.

commit d6e0152d9a0262038ab6102317298d1c51333062
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Nov 5 15:53:10 2026 -0600

    HACKING: Revise.
    
    Drop mentions of "Copyright-paperwork-exempt", as they're potentially
    confusing: GNU projects that require copyright assignment use that
    annotation, and we don't impose that requirement.
    
    Thanks to Ingo Schwarze for the discussion.
---
 HACKING | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/HACKING b/HACKING
index cab3718db..5ff75eb23 100644
--- a/HACKING
+++ b/HACKING
@@ -332,10 +332,8 @@ What To Do
   original expression.
 
   Where a change produces a net increase of 15 lines or more but _still_
-  seems robotic or unoriginal, consider (1) applying the annotation
-  "Copyright-paperwork-exempt: yes" to the Git commit log message, and
-  (2) recording, in the corresponding commit log message, the robotic
-  procedure that produced the change.
+  seems robotic or unoriginal, consider recording, in the corresponding
+  commit log message, the robotic procedure that produced the change.
 
   If a change contains what would otherwise be legally significant
   original expression that gets "swamped" by removal of other material--
@@ -384,9 +382,8 @@ What To Do
   is "legally significant" per the 15-line threshold.  But even a new
   file of legally significant size does not merit a copyright notice if
   it does not constitute original, non-robotic expression as discussed
-  above.  In that case, include "Copyright-paperwork-exempt: yes" in the
-  Git commit log message.  To summarize, the same rules apply to new
-  files as to changes to existing ones.
+  above.  To summarize, the same rules apply to new files as to changes
+  to existing ones.
 
 * In UTF-8-encoded files, it is fine to use a true copyright sign
   (Unicode U+00A9).  Place it in the notice between the word "Copyright"

_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit

Reply via email to