From: Victoria Dye <vdye@github.com>
To: Vivan Garg <gvivan6@gmail.com>, git@vger.kernel.org
Cc: nasamuffin@google.com
Subject: Re: [PATCH v2 0/1] MyFirstContribution: add note about SMTP server config
Date: Wed, 22 Feb 2023 22:24:18 -0800 [thread overview]
Message-ID: <be5fbb48-4599-f6d0-e7c3-cf0470ce8bbd@github.com> (raw)
In-Reply-To: <20230223054040.30088-1-gvivan6@gmail.com>
Vivan Garg wrote:
> Vivan Garg (1):
> MyFirstContribution: add note about SMTP server config
>
> Documentation/MyFirstContribution.txt | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Range-diff against v1:
> 1: bd9bc70307 < -: ---------- Documentation/MyFirstContribution: add setup template for git send-email
> -: ---------- > 1: d295b4d913 MyFirstContribution: add note about SMTP server config
Since you also did this in your microproject, it's worth pointing out: you
don't need a cover letter for a single-patch submission (see "Bonus Chapter:
One-Patch Changes" in MyFirstContribution). You can include the range-diff
below the '---' line (i.e., below the commit message) in your patch.
next prev parent reply other threads:[~2023-02-23 6:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 1:13 [PATCH] Documentation/MyFirstContribution: add setup template for git send-email Vivan Garg
2023-02-22 21:18 ` Victoria Dye
2023-02-23 4:09 ` Vivan Garg
2023-02-23 5:40 ` [PATCH v2 0/1] MyFirstContribution: add note about SMTP server config Vivan Garg
2023-02-23 5:40 ` [PATCH v2 1/1] " Vivan Garg
2023-02-23 6:23 ` Victoria Dye
2023-02-23 6:24 ` Victoria Dye [this message]
2023-02-23 6:47 ` [PATCH v2 0/1] " Vivan Garg
2023-02-23 8:27 ` [PATCH v3] " Vivan Garg
2023-02-23 8:45 ` Benson Muite
2023-02-23 9:20 ` Vivan Garg
2023-02-23 10:37 ` Benson Muite
2023-02-26 0:49 ` Vivan Garg
2023-02-26 13:19 ` Bagas Sanjaya
2023-02-26 13:07 ` Bagas Sanjaya
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be5fbb48-4599-f6d0-e7c3-cf0470ce8bbd@github.com \
--to=vdye@github.com \
--cc=git@vger.kernel.org \
--cc=gvivan6@gmail.com \
--cc=nasamuffin@google.com \
/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.
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 NNTP newsgroup(s).