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

Re: [GSoC][RFC/PATCH 0/1]

From
Thomas Gummerer <t.gummerer@gmail.com>
Date
Mar 15, 2019, 22:39 UTC
Message-ID
<20190315223958.GI16414@hank.intra.tgummerer.com>
In-Reply-To
<20190315150142.20672-1-jkapil.cs@gmail.com>
On 03/15, jkapil.cs@gmail.com wrote:
> From: Kapil <jkapil.cs@gmail.com>
>

The cover letter should give reviewers a short introduction what a patch series is about. It's often not worth including a cover letter if there is only a single patch, or only a couple of patches.

It is okay to send a cover letter for a single patch, however it should include some explanation for the patch series, and not just duplicate what's said in the commit message of the actual patch. An empty cover letter as this one here is just noise, and should be omitted.

Show 11 quoted lines
> Kapil (1):
>   userdiff - support shell script
> 
>  t/t4018-diff-funcname.sh | 1 +
>  t/t4034-diff-words.sh    | 1 +
>  userdiff.c               | 5 +++++
>  3 files changed, 7 insertions(+)
> 
> -- 
> 2.14.2
>
Previous: Thomas GummererNext: Thomas Gummerer
Message 4 of 5 in “[GSoC][RFC/PATCH 0/1]”
  1. jkapil.cs@gmail.comMar 15, 2019
  2. [GSoC][RFC/PATCH 1/1] userdiff - support shell scriptjkapil.cs@gmail.com, Mar 15, 2019
  3. Thomas GummererMar 15, 2019
  4. Thomas GummererMar 15, 2019
  5. Thomas GummererMar 16, 2019

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.