From: Ævar Arnfjörð Bjarmason Date: Wed, 28 Jul 2010 14:11:25 +0000 (+0000) Subject: SubmittingPatches: Cite the 50 char subject limit X-Git-Tag: v1.7.3-rc0~105 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=43e331e6ee46ba156d43f1fd3ebc91cc35575e47;p=git.git SubmittingPatches: Cite the 50 char subject limit Change the SubmittingPatches recommendations to mention the 50 character soft limit on patch subject lines. 50 characters is the soft limit mentioned in git-commit(1) and gittutorial(7), it's also the point at which Gitweb, GitHub and various other Git front ends start abbreviating the commit message. Signed-off-by: Ævar Arnfjörð Bjarmason Signed-off-by: Junio C Hamano --- diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 2e18f6b44..ece3c7748 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -7,7 +7,8 @@ Checklist (and a short version for the impatient): before committing - do not check in commented out code or unneeded files - the first line of the commit message should be a short - description and should skip the full stop + description (50 characters is the soft limit, see DISCUSSION + in git-commit(1)), and should skip the full stop - the body should provide a meaningful commit message, which: - uses the imperative, present tense: "change", not "changed" or "changes".