]> git.ipfire.org Git - thirdparty/git.git/commit
projects / thirdparty / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 92999a4) | patch
CodingGuidelines: a handful of error message guidelines
authorJunio C Hamano <gitster@pobox.com>
Wed, 27 Nov 2024 13:23:45 +0000 (22:23 +0900)
committerJunio C Hamano <gitster@pobox.com>
Fri, 29 Nov 2024 01:36:06 +0000 (10:36 +0900)
commit168ebb7159584df425797dd13d8d8986dc08051e
tree8170a44562922de505335053f4560025586838e9tree | snapshot
parent92999a42db1c5f43f330e4f2bca4026b5b81576fcommit | diff
CodingGuidelines: a handful of error message guidelines

It is more efficient to have something in the coding guidelines
document to point at, when we want to review and comment on a new
message in the codebase to make sure it "fits" in the set of
existing messages.

Let's write down established best practice we are aware of.

Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/CodingGuidelines diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.