gbranden pushed a commit to branch master
in repository groff.

commit 79aef0491033f67d5c63889c0e75733731df754b
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Nov 5 15:58:49 2026 -0600

    HACKING: Clarify.
    
    If you can "golf" your change down to something smaller than your
    original editing sequence, that's not only fine but reinforces the
    argument for the change being of "robotic" nature.
---
 HACKING | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/HACKING b/HACKING
index 43a0dcd00..20d868da5 100644
--- a/HACKING
+++ b/HACKING
@@ -333,7 +333,7 @@ What To Do
 
   Where a change produces a net increase of 15 lines or more but _still_
   seems robotic or unoriginal, consider recording, in the corresponding
-  commit log message, the robotic procedure that produced the change.
+  commit log message, a robotic procedure that reproduces the change.
 
   If a change contains what would otherwise be legally significant
   original expression that gets "swamped" by removal of other material--

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

Reply via email to