On Thu, Jan 27, 2022 at 11:02:57AM -0800, Junio C Hamano wrote: > > We give a guidance for proposed log message to write problem > statement first, followed by the reasoning behind, and recipe for, > the solution. Clarify that we describe the situation _before_ the > proposed patch is applied in the present tense (not in the past > tense e.g. "we used to do X, but thanks to this commit we now do Y") > for consistency. > > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- > Documentation/SubmittingPatches | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches > index 92b80d94d4..7225a0fb52 100644 > --- a/Documentation/SubmittingPatches > +++ b/Documentation/SubmittingPatches > @@ -142,6 +142,13 @@ The body should provide a meaningful commit message, which: > > . alternate solutions considered but discarded, if any. > > +[[present-tense]] > +The problem statement that describes the status quo is written in the > +present tense. Write "The code does X when it is given input Y", > +instead of "The code used to do Y when given input X". You do not > +have to say "Currently"---the status quo in the problem statement is > +about the code _without_ your change, by project convention. > + The writing sample helps a lot here. "Present tense" is a poor example, but I think it's common for native language speakers to know less about specific grammar words (like "imperative mood" below), even though they can often instinctively tell what form you're describing when seeing a sample. As for the norm itself, I think it is a good one, and I've seen it pointed out in code reviews frequently. Thanks. Reviewed-by: Emily Shaffer <emilyshaffer@xxxxxxxxxx> > [[imperative-mood]] > Describe your changes in imperative mood, e.g. "make xyzzy do frotz" > instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy > -- > 2.35.0-177-g7d269f5170 >
