Files
git/Documentation
Junio C Hamano 168ebb7159 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>
2024-11-29 10:36:06 +09:00
..
2024-10-04 14:21:43 -07:00
2024-11-25 12:32:21 +09:00
2024-07-23 11:02:52 -07:00
2024-09-23 12:47:36 -07:00
2024-09-23 12:47:36 -07:00
2024-06-17 15:55:56 -07:00
2023-11-26 10:07:05 +09:00
2023-06-12 13:52:51 -07:00
2024-08-16 09:46:25 -07:00
2023-10-09 12:06:29 -07:00
2023-11-26 10:07:05 +09:00
2023-12-26 11:06:55 -08:00
2024-02-21 10:02:55 -08:00
2023-10-09 12:06:29 -07:00
2023-06-12 13:52:51 -07:00
2023-06-12 13:52:51 -07:00
2024-01-02 13:51:30 -08:00
2024-05-07 10:06:03 -07:00
2024-04-19 12:38:50 +02:00
2023-12-14 14:38:07 -08:00
2023-12-26 11:06:55 -08:00
2024-09-23 12:47:36 -07:00
2023-11-26 10:07:05 +09:00