From: Christian Couder <christian.couder@gmail.com>
To: Caleb Tillman <caleb.tillman@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [Outreachy] [PATCH 0/1]
Date: Sat, 17 Oct 2020 08:43:59 +0200 [thread overview]
Message-ID: <CAP8UFD3=pByaH-bFFo8VVSqt_NVPwpHLx0RQyCDwfWV8OL7TRw@mail.gmail.com> (raw)
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!
prev parent reply other threads:[~2020-10-17 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 2:43 [Outreachy] [PATCH 0/1] Caleb Tillman
2020-10-17 2:43 ` [PATCH 1/1] Microproject - Use debug-friendly test_path_is_* functions Caleb Tillman
2020-10-17 7:19 ` Christian Couder
2020-10-17 6:43 ` Christian Couder [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3=pByaH-bFFo8VVSqt_NVPwpHLx0RQyCDwfWV8OL7TRw@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=caleb.tillman@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).