gbranden pushed a commit to branch master
in repository groff.
commit 2fc80274b3bce06b1fa71c09f4670ac13d61fe53
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Dec 18 11:03:55 2025 -0600
gdiffmk(1): Revise copyright notice.
Ratchet back ending year of FSF copyright notice to 2016, 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):
2017 f39e9e836b man pages: Replace `asymmetric quotation style'. (+1)
2018 4ab68de177 **/*.man: Rationalize synopses. (+2)
2019 699ac6598d *.[157].man: Save and restore compatibility mode. (+11)
2020 0afc013230 man pages: Regularize synopsis style. (+3)
2020 af55ca5985 man page: Fix style nit. (+1)
2021 7bafea3d92 [man pages]: Remove compatibility save register. (+1)
2021 c424ecfe90 [man pages]: Stop using .OP macro. (+4)
2022 d72b4b7b94 [man pages]: Update summary descriptions. (+2)
2023 b0ed622fec gdiffmk(1): Update maintenance status. (+5)
2023 a9767ace3d [man pages]: Define page-local `MR` fallback. (+15)
2023 cbb1d84e40 gdiffmk(1): Fix content and style nits. (+5)
2023 ccf1006175 contrib/gdiffmk/gdiffmk.sh: Refactor. (+29)
2023 d4b0bce652 [gdiffmk]: Abbreviate usage message. (+3)
2024 a08908f982 [man]: Revise and expand `SY` and `YS` behavior. (+2)
2025 3baa8cf5f6 gdiffmk(1): Recast some option descriptions. (+3)
2025 a8b6ad72fa gdiffmk(1): Clarify description. (+10)
2025 88300e4f5b [gdiffmk]: Sync Usage() description with man page. (+3)
Commits other than a9767ace3d and ccf1006175 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 "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
---
contrib/gdiffmk/gdiffmk.1.man | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/contrib/gdiffmk/gdiffmk.1.man b/contrib/gdiffmk/gdiffmk.1.man
index 1662e6772..142f0a8c5 100644
--- a/contrib/gdiffmk/gdiffmk.1.man
+++ b/contrib/gdiffmk/gdiffmk.1.man
@@ -9,7 +9,8 @@ files
.\" Legal Terms
.\" ====================================================================
.\"
-.\" Copyright 2004-2025 Free Software Foundation, Inc.
+.\" Copyright 2004-2016 Free Software Foundation, Inc.
+.\" 2017-2025 G. Branden Robinson
.\"
.\" This file is part of gdiffmk, which is part of groff, the GNU roff
.\" typesetting system.
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
