gbranden pushed a commit to branch master
in repository groff.
commit 0c3d2e49946af36f674c5d88ebf695e77fd1a1e1
Author: G. Branden Robinson <[email protected]>
AuthorDate: Mon Feb 9 18:37:13 2026 -0600
HACKING: Clarify copyright line-count procedure.
---
HACKING | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/HACKING b/HACKING
index 5bb6d683c..eeafd74c9 100644
--- a/HACKING
+++ b/HACKING
@@ -205,11 +205,12 @@ What To Do
further guidance from that manual, in groff we ignore the issue of
line length and interpret "15 lines" as requiring a _net increase_ in
a file's line count of at least that magnitude, as calculated by
- taking the output of "git diff --stat" on the file and subtracting
- lines removed from lines added, a procedure that can result in a
- nonpositive number. This rule has the advantage that it tends to
- exclude voluminous but robotic changes, as one might make with "sed
- -i", which seldom constitute "original expression".
+ taking the output of "git diff --stat" on the file (or "git log
+ --stat" on a relevant commit to it) and subtracting lines removed from
+ lines added, a procedure that can result in a nonpositive number.
+ This rule has the advantage that it tends to exclude voluminous but
+ robotic changes, as one might make with "sed -i", which seldom
+ constitute "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
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
