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

Re: [Outreachy] [PATCH 0/1]

From
Christian Couder <christian.couder@gmail.com>
Date
Oct 17, 2020, 06:43 UTC
Message-ID
<CAP8UFD3=pByaH-bFFo8VVSqt_NVPwpHLx0RQyCDwfWV8OL7TRw@mail.gmail.com>
In-Reply-To
<20201017024353.189792-1-caleb.tillman@gmail.com>
On Sat, Oct 17, 2020 at 8:06 AM Caleb Tillman <caleb.tillman@gmail.com> wrote:
>
> *** BLURB HERE ***

Cover letters like this are about giving context for a series of patches. As there is only one patch (1/1) in the series, the context in the patch itself should suffice, so there is no real need for a cover letter like this if there is only one patch.

When there is a real need for a cover letter though, the title of the cover letter should explain what the patch series is about and "*** BLURB HERE ***" in the body of the cover letter should be replaced by text that explains the context and the reason for the patch series.

Thanks!
Previous: Christian Couder
Message 4 of 4 in “[Outreachy] [PATCH 0/1]”
  1. Caleb TillmanOct 17, 2020
  2. 1/1 Microproject - Use debug-friendly test_path_is_* functions.Caleb Tillman, Oct 17, 2020
  3. Christian CouderOct 17, 2020
  4. Christian CouderOct 17, 2020

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.