gbranden pushed a commit to branch master
in repository groff.

commit ef0eaa88b6d901b87b22b37f43425a9dac002414
Author: G. Branden Robinson <[email protected]>
AuthorDate: Sun Nov 30 15:09:54 2025 -0600

    src/roff/troff/number.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)
    83657bdfac [troff]: Revise some diagnostic messages. (+2)
    515b35b9b1 [troff]: Refactor and fix code style nits. (+9)
    c4f2abed96 [troff]: Trivially refactor (`tem` -> `position`). (+1)
    95d04688e7 src/roff/troff/number.cpp: Note non-wraparound. (+1)
    40d5127967 [troff]: Fix Savannah #64301 (7/15). (+7)
    f3a331e907 [troff]: Fix Savannah #64301 (12/15). (+7)
    b4f9d7010d [troff]: Fix Savannah #64301 (13/15). (+3)
    05bcb560c8 src/roff/troff/number.cpp: Slightly refactor. (+12)
    a3e0a4fe33 src/roff/troff/number.cpp: Fix Savannah #64301. (+20)
    17f18cc8cb [troff]: Fix Savannah #66001 (saturating arith). (+18)
    4d8f38aec0 [troff]: Fix Savannah #66150 (`p` and `s` units). (+1)
    6f08ec9815 [troff]: Fix Savannah #60995 (`f` scaling unit). (+8)
    12809b85e3 [troff]: Trivially refactor. (+1)
    47d3b00ec9 [troff]: Fix syntax warning diagnostic regression. (+4)
    
    Commits a3e0a4fe33 and 17f18cc8cb 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 lines 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/number.cpp | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/roff/troff/number.cpp b/src/roff/troff/number.cpp
index ad5819984..405bc0433 100644
--- a/src/roff/troff/number.cpp
+++ b/src/roff/troff/number.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

Reply via email to