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

Re: [PATCH 1/1] [OUTREACHY] Fixed add.c file to conform to guidelines when using die() listed in issue #635

From
Christian Couder <christian.couder@gmail.com>
Date
Oct 9, 2023, 07:27 UTC
Message-ID
<CAP8UFD35DBBwQ1Mgc+NGVoh1ReLncAz9OJF3Yj++FFrESw8rtw@mail.gmail.com>
In-Reply-To
<20231009011652.1791-1-naomi.ibeh69@gmail.com>
On Mon, Oct 9, 2023 at 3:17 AM Naomi Ibe <naomi.ibeh69@gmail.com> wrote:
>
> From: Naomi <naomi.ibeh69@gmail.com>

First the subject should start, after "[PATCH 1/1][Outreachy]", with the area of the code you are changing followed by ":", so here "add:" (no need for ".c").

Also even if the subject gives a lot of information already, it's better to use the body of the commit message to give a bit more context and details. For example here either the subject or the body of the commit message should say which specific guideline(s) the patch is enforcing.

Show 5 quoted lines
> Signed-off-by: Naomi Ibe <naomi.ibeh69@gmail.com>
> ---
>  builtin/add.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
Otherwise the patch looks good to me.
Thanks!
Previous: Naomi IbeNext: Naomi Ibe
Message 2 of 4 in “[OUTREACHY] Fixed add.c file to conform to guidelines when using die() listed in issue #635”
  1. 1/1 [OUTREACHY] Fixed add.c file to conform to guidelines when using die() listed in issue #635Naomi Ibe, Oct 9, 2023
  2. Christian CouderOct 9, 2023
  3. Naomi IbeOct 9, 2023
  4. Christian CouderOct 9, 2023

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.