gbranden pushed a commit to branch master
in repository groff.

commit 969322600fe4bcd3452de5ba676221436cda15c8
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Dec 18 10:45:27 2025 -0600

    src/roff/nroff/nroff.sh: Revise copyright notice.
    
    Ratchet back ending year of FSF copyright notice to 2021, 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):
    
    2019 5445eacd1c nroff.sh: Make minor tweaks. (+3)
    2020 dd725dce80 nroff: Implement -P and -V options. (+35)
    2020 2a9e09c033 Repair nroff test case. (+3)
    2021 b4de44f028 [[gnt]roff]: Make usage messages more accurate. (+1)
    2021 2b955c571c [nroff]: Fix Savannah #60943. (+18)
    2021 8ca88a9c72 [nroff]: Improve portability. (+3)
    2021 d7378739ca [nroff]: Update portability comments. (+4)
    2021 7da376ae98 [nroff]: Fix oversights. (+1)
    2022 cf62182939 [nroff]: Update usage message. (+4)
    2024 4ec50d1366 [nroff]: Describe program when asked for `--help`. (+5)
    2024 78394f9f5b [nroff]: Support `-a`, `-D`, `-I`, & `-Z` options. (+14)
    2024 24d4975ebe [nroff]: Support argument clustering. (+28)
    2024 e05cf6d3b3 [nroff]: Work around substandard Unix systems. (+17)
    2024 c34c6cc58c [nroff]: Improve shell behavior check. (+6)
    
    Commits other than dd725dce80, 2b955c571c, 24d4975ebe, and e05cf6d3b3
    meet the 15-line threshold 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 spuriously "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/nroff/nroff.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/roff/nroff/nroff.sh b/src/roff/nroff/nroff.sh
index 5128e5dcb..6b029ca9a 100644
--- a/src/roff/nroff/nroff.sh
+++ b/src/roff/nroff/nroff.sh
@@ -2,7 +2,8 @@
 #
 # Emulate nroff with groff.
 #
-# Copyright 1992-2025 Free Software Foundation, Inc.
+# Copyright 1992-2021 Free Software Foundation, Inc.
+#           2019-2024 G. Branden Robinson
 #
 # Written by James Clark, Werner Lemberg, and G. Branden Robinson.
 #

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

Reply via email to