diff options
| author | Elijah Newren <newren@gmail.com> | 2023-10-08 06:45:09 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2023-10-09 12:06:29 -0700 |
| commit | ce14cc0b00098201f967346955804abd774174ea (patch) | |
| tree | 87da2bbac39b08973b8a5e3944ddf7a21141a392 /Documentation/CodingGuidelines | |
| parent | 859a6d6045e338a337cb7499100b1fa31c367fbf (diff) | |
| download | git-ce14cc0b00098201f967346955804abd774174ea.tar.gz | |
documentation: fix subject/verb agreement
Diff best viewed with --color-diff.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/CodingGuidelines')
| -rw-r--r-- | Documentation/CodingGuidelines | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines index 99b22ff234..c494e07460 100644 --- a/Documentation/CodingGuidelines +++ b/Documentation/CodingGuidelines @@ -40,7 +40,7 @@ As for more concrete guidelines, just imitate the existing code contributing to). It is always preferable to match the _local_ convention. New code added to Git suite is expected to match the overall style of existing code. Modifications to existing -code is expected to match the style the surrounding code already +code are expected to match the style the surrounding code already uses (even if it doesn't match the overall style of existing code). But if you must have a list of rules, here are some language |