aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/CodingGuidelines
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-10-30 07:09:56 +0900
committerJunio C Hamano <gitster@pobox.com>2023-10-30 07:09:56 +0900
commit1551066dc5724d2bfdc88e8f920eb64077db9dfa (patch)
treeadeb52a809f73ec3196cb58fce998c6cc8138848 /Documentation/CodingGuidelines
parent26dd307cfaabe3d3f0b01aad64969e76a317811a (diff)
parentffbf6a748d0dd7c9377ec99166ac132c95a5b96a (diff)
downloadgit-1551066dc5724d2bfdc88e8f920eb64077db9dfa.tar.gz
Merge branch 'jc/update-list-references-to-lore'
Doc update. * jc/update-list-references-to-lore: doc: update list archive reference to use lore.kernel.org
Diffstat (limited to 'Documentation/CodingGuidelines')
-rw-r--r--Documentation/CodingGuidelines2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
index c494e07460..8d3a467c01 100644
--- a/Documentation/CodingGuidelines
+++ b/Documentation/CodingGuidelines
@@ -24,7 +24,7 @@ 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