summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-11-02 16:53:26 +0900
committerJunio C Hamano <gitster@pobox.com>2023-11-02 16:53:27 +0900
commita40b8e9197042f727c6f6e57e008523265839079 (patch)
tree279c730c67f154a4d9c61e4b0bd1665a150891c6
parent3a16179bfbe8ef088164a7a55ef9f566828499bc (diff)
parentffbf6a748d0dd7c9377ec99166ac132c95a5b96a (diff)
downloadgit-a40b8e9197042f727c6f6e57e008523265839079.tar.gz
Merge branch 'jc/update-list-references-to-lore' into maint-2.42
Doc update. * jc/update-list-references-to-lore: doc: update list archive reference to use lore.kernel.org
-rw-r--r--Documentation/CodingGuidelines2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index 65af8d82ce..9495df835d 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -24,7 +24,7 @@ code. For Git in general, a few rough rules are:
"Once it _is_ in the tree, it's not really worth the patch noise to
go and fix it up."
- Cf. http://lkml.iu.edu/hypermail/linux/kernel/1001.3/01069.html
+ Cf. https://lore.kernel.org/all/20100126160632.3bdbe172.akpm@linux-foundation.org/
- Log messages to explain your changes are as important as the
changes themselves. Clearly written code and in-code comments