From: Junio C Hamano <gitster@pobox.com>
To: Weijie Yuan <wy@wyuan.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/6] SubmittingPatches: clarify expected structure of commit log message
Date: Sun, 12 Jul 2026 09:07:32 -0700 [thread overview]
Message-ID: <xmqq7bn042ez.fsf@gitster.g> (raw)
In-Reply-To: <alOplirhJxIkpDYh@wyuan.org> (Weijie Yuan's message of "Sun, 12 Jul 2026 22:49:58 +0800")
Weijie Yuan <wy@wyuan.org> writes:
>> +2. **Solution (The Approach)**:
>> +3. **Command (The Instruction)**:
>> + [[imperative-mood]]
>> + Command the codebase to change. Write this in the **imperative
>> + mood** (e.g., "make xyzzy do frotz" instead of "This patch makes
>> + xyzzy do..." or "I changed xyzzy..."), as if you are giving orders
>> + to the codebase to change its behavior.
>
> Stopped and confused for a moment. I am not sure that "Command" belongs
> alongside "Observation" and "Solution" as a third part of the message.
> Sometimes the command still describes the solution. In other words,
> Solution and Command seem not to be logically completely separable.
I do not think "Command the codebase to change" is a good phrasing.
It would have been better to highlight the distinction between the
design of the solution (approach) and the implementation. Perhaps
2. Design (The Approach)
3. Implementation (The Changes)
[[imperative-mood]]
Describe how the change is implemented. Write this in the
imperative mood. ...
or something?
>> +#### Formatting and Style Guidelines
>
> Perhaps using "====" here would be in harmony with the existing content.
Indeed.
>> +* **The Body**:
>> + * Explain the *why* rather than repeating the *what* of the diff.
>> + * Try to make the explanation self-contained. Avoid relying on
>> + external URLs (like mailing list archives) as the sole
>> + explanation; summarize the relevant points of the discussion
>> + instead.
>> + * Wrap lines to 68-72 columns.
>
> MyFirstContribution:
> This commit message is intentionally formatted to 72 columns per line
>
> Should we update both?
Perhaps just to stick to "around 70".
I do not think the defaults in various editors matter.
The "wrap around 70 columns" rule exists so that in a text based
email exchange, where you lose two columns to leading "> " when
quoted, and an additional column with each subsequent reply, the
lines will still fit on standard 80-column terminals.
Thanks.
next prev parent reply other threads:[~2026-07-12 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 19:26 [PATCH 0/6] Update Contributor Guides Junio C Hamano
2026-07-11 19:26 ` [PATCH 1/6] SubmittingPatches: clarify expected structure of commit log message Junio C Hamano
2026-07-12 14:49 ` Weijie Yuan
2026-07-12 16:07 ` Junio C Hamano [this message]
2026-07-13 14:14 ` Weijie Yuan
2026-07-12 20:26 ` Michael Montalbo
2026-07-13 0:07 ` Junio C Hamano
2026-07-13 14:14 ` Weijie Yuan
2026-07-11 19:26 ` [PATCH 2/6] MyFirstContribution: what if I don't get a reply? Junio C Hamano
2026-07-11 19:26 ` [PATCH 3/6] MyFirstContribution: carrying over trailers Junio C Hamano
2026-07-11 19:26 ` [PATCH 4/6] MyFirstContribution: clarify that 'seen' does not mean acceptance Junio C Hamano
2026-07-12 18:08 ` Matt Hunter
2026-07-12 19:04 ` Junio C Hamano
2026-07-11 19:26 ` [PATCH 5/6] SubmittingPatches: clarify the meaning of "Will queue" Junio C Hamano
2026-07-11 19:26 ` [PATCH 6/6] SubmittingPatches: clarify the writing style of whats-cooking Junio C Hamano
2026-07-12 20:41 ` Michael Montalbo
2026-07-13 4:20 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq7bn042ez.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wy@wyuan.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox