gbranden pushed a commit to branch master
in repository groff.
commit bf42533d6fbb0d3511def0061c1f3419f791ce50
Author: G. Branden Robinson <[email protected]>
AuthorDate: Thu Sep 4 06:32:09 2025 -0500
HACKING: Clarify item.
When justifying "original work", we want not only the (abbreviated) Git
hashes, but the human-intelligible change summaries.
---
HACKING | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING
index d5783a50c..9228adc3a 100644
--- a/HACKING
+++ b/HACKING
@@ -121,8 +121,9 @@ Updating Copyright Notices
accrete original status over time or a series of commits, it's fine to
later update the notice to include the relevant (hopefully current)
year in a stand-alone commit. Use "git log --oneline" on a file to
- gather commit IDs that justify the update and put them in the commit
- message so that other people understand the basis of your claim.
+ gather commit IDs and change summaries that justify the update and put
+ them in the commit message so that other people understand the basis
+ of your claim.
* It's okay to simply report a range of years in the copyright notice
instead of a comma-separated list. As far as GBR knows there is no
_______________________________________________
groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
