diff options
| author | Junio C Hamano <gitster@pobox.com> | 2024-11-27 22:23:45 +0900 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-11-29 10:36:06 +0900 |
| commit | 168ebb7159584df425797dd13d8d8986dc08051e (patch) | |
| tree | 8170a44562922de505335053f4560025586838e9 /commit.c | |
| parent | 92999a42db1c5f43f330e4f2bca4026b5b81576f (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>
Diffstat (limited to 'commit.c')
0 files changed, 0 insertions, 0 deletions