git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] [PATCH v2] gpg-interface.c: trim CR only before LF

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 17, 2025, 19:12 UTC
Message-ID
<xmqqo6q5z6iu.fsf@gitster.g>
In-Reply-To
<CAP8UFD2sdvkv_ZqiLZU9k5zF+tM3UTQ8+mJjziRZGzOra6dMFA@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 20 quoted lines
> On Thu, Oct 16, 2025 at 10:04 PM Okhuomon Ajayi
> <okhuomonajayi54@gmail.com> wrote:
>>
>> Problem:
>> The function remove_cr_after() stripped CRs blindly. The comment suggested
>> NEEDSWORK: trim only CRs before LF.
>
> We use the present tense to talk about the current situation. In
> "Documentation/SubmittingPatches" there is:
>
> "[[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."
>
> Also you don't need to prefix this part with "Problem:". We should
> understand from the description of the status quo that the situation
> is not good and should be improved.

Thanks for the above two pieces of advice. The latter follows if messages of all commits follow a simple convention that we have been following, which is that the usual way to compose a log message of this project is to

 - Give an observation on how the current system works in the
   present tense (so no need to say "Currently X is Y", or
   "Previously X was Y" to describe the state before your change;
   just "X is Y" is enough), and discuss what you perceive as a
   problem in it.
 - Propose a solution (optional---often, problem description
   trivially leads to an obvious solution in reader's minds).
 - Give commands to somebody editing the codebase to "make it so",
   instead of saying "This commit does X".
in this order.

Perhaps we should write it somewhere in the introductory text designed to help applicants of mentoring programs like Outreachy and GSoC?

Thanks.
Previous: Christian Couder
Message 3 of 3 in “gpg-interface.c: trim CR only before LF”
  1. [PATCH v2] gpg-interface.c: trim CR only before LFOkhuomon Ajayi, Oct 16, 2025
  2. Christian CouderOct 17, 2025
  3. Junio C HamanoOct 17, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.