gbranden pushed a commit to branch master
in repository groff.
commit 7d2fef66a8db1ce81894ce8230693d9c87a815bb
Author: G. Branden Robinson <[email protected]>
AuthorDate: Wed Mar 11 18:31:37 2026 -0500
HACKING: Revise material on copyright notices.
* Clarify guidance on adding files.
* Drop phrase copied from a commit log. "This notice" has no referent
in the observed context.
---
HACKING | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/HACKING b/HACKING
index 4442612fc..24f3fd0a1 100644
--- a/HACKING
+++ b/HACKING
@@ -282,9 +282,9 @@ What To Do
is "legally significant" per the 15-line threshold. But even a new
file of legally significant size does not merit a copyright notice if
it does not constitute original, non-robotic expression as discussed
- above. Include "Copyright-paperwork-exempt: yes" in the Git commit
- log message. To summarize, the same rules apply to new files as to
- changes to existing ones.
+ above. In that case, include "Copyright-paperwork-exempt: yes" in the
+ Git commit log message. To summarize, the same rules apply to new
+ files as to changes to existing ones.
* In UTF-8-encoded files, it is fine to use a true copyright sign
(Unicode U+00A9). Place it in the notice between the word "Copyright"
@@ -303,7 +303,7 @@ What To Do
unavailable. Nowadays, its advice is that "c" (note lowercase) is an
"acceptable variant", that _may_ retain the efficacy of the copyright
notice. The word "copyright", spelled out in full, also suffices per
- that resource, and is already present in this notice.
+ that resource.
See <https://www.copyright.gov/circs/circ03.pdf>.
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
