gbranden pushed a commit to branch master
in repository groff.
commit 46d74078b1495330afcf1f2841c80dd8bd4756d7
Author: G. Branden Robinson <[email protected]>
AuthorDate: Sun Nov 30 15:40:33 2025 -0600
src/roff/troff/reg.cpp: Revise copyright notice.
Ratchet back ending year of FSF copyright notice to 2020, reflecting the
date of the last contribution to this file by anyone but me.
Add copyright notice for myself. I have never executed copyright
assignment paperwork with the FSF, so my "legally significant"[1]
changes to this file can't be under the FSF's copyright.
Justification (commit ID, summary, net lines added by commit):
9aa4cae7b3 [troff]: Boolify members of `token` class. (+5)
0c5e4b9d8b [troff]: Fix Savannah #63149. (+3)
9b1161e6bf [troff]: Do less unconditional #including. (+6)
110f520e42 [troff]: Clarify error diagnostics. (+1)
2bd122bf56 [troff]: Fix Savannah #64240 (warn of nr garbage). (+6)
956955c663 [troff]: Fix Savannah #63202 (1/3). (+7)
1277744e72 [troff]: Improve diagnostic messages. (+1)
2f6a72b9e3 [troff]: Exercise warning category "missing" more. (+41)
88ddddc8f8 [troff]: Make `pnr` report interpolation format. (+3)
13866fdf0b [troff]: `pnr` request now accepts arguments. (+15)
12374f8dbb [troff]: Adjust `af` error diagnostic wording. (+1)
97b08fa3ee [troff]: Tweak argumentful `pnr` output. (+6)
c6fe97b3d4 [troff]: Improve input validation. (+13)
5dcf31ee54 [troff]: `pnr` request reports autoincr amounts. (+28)
dd517efbb9 [troff]: Favor C++ cast operators over those of C. (+2)
13c19f1e08 src/roff/troff/reg.cpp: Add assertion. (+1)
e074c55f27 [troff]: Fix code style nit. (+4)
Commits 2f6a72b9e3, 13866fdf0b, and 5dcf31ee54 each independently pass
the threshold, as do the others taken cumulatively. (The GNU
Maintainers' Guide does not advise for or against a cumulative
interpretation. Applying rigidly simplistic rules supporting or
opposing such an interpretation each lead to seeming absurdities. On
the one hand, 15 different minor changes, like incrementing an integer,
to a single line of code--or code comment--in the source file could
become "legally significant". On the other hand, if a person
contributes a net _deletion_ of lines overall, perhaps by eliminating
dead code or withdrawn functionality, they could prevent recognition of
their own contribution(s) of any size as "legally significant" as long
as those changes added fewer than <lines deleted> + 15. Counting lines
of code may be as poor a metric of copyrightability as it is of
programmer productivity.[2])
[1] "A change of just a few lines (less than 15 or so) is not legally
significant for copyright." Conversely, >= 15 lines would be.
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
[2]
https://www.researchgate.net/publication/335535826_The_End_to_the_Myth_of_Individual_Programmer_Productivity
---
src/roff/troff/reg.cpp | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/roff/troff/reg.cpp b/src/roff/troff/reg.cpp
index de010981a..08ff61c4e 100644
--- a/src/roff/troff/reg.cpp
+++ b/src/roff/troff/reg.cpp
@@ -1,4 +1,6 @@
-/* Copyright 1989-2025 Free Software Foundation, Inc.
+/* Copyright 1989-2020 Free Software Foundation, Inc.
+ 2021-2025 G. Branden Robinson
+
Written by James Clark ([email protected])
This file is part of groff.
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
