git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivan Garg <v.garg.work@gmail.com>
To: Victoria Dye <vdye@github.com>
Cc: Vivan Garg <gvivan6@gmail.com>,
	git@vger.kernel.org, nasamuffin@google.com
Subject: Re: [PATCH v2 0/1] MyFirstContribution: add note about SMTP server config
Date: Wed, 22 Feb 2023 23:47:41 -0700	[thread overview]
Message-ID: <CADupsJP6T8OFCEJsyy4uFHvk8P-CfBODYpcR1n5jEWUiAND4Rw@mail.gmail.com> (raw)
In-Reply-To: <be5fbb48-4599-f6d0-e7c3-cf0470ce8bbd@github.com>

> 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.

I didn't include the cover letter in either v1 but thought the range-diff was
important so I kept it in both v2's. Next time, I'll just put it below
the commit
message. Thanks!

  reply	other threads:[~2023-02-23  6:48 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   ` [PATCH v2 0/1] " Victoria Dye
2023-02-23  6:47     ` Vivan Garg [this message]
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=CADupsJP6T8OFCEJsyy4uFHvk8P-CfBODYpcR1n5jEWUiAND4Rw@mail.gmail.com \
    --to=v.garg.work@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gvivan6@gmail.com \
    --cc=nasamuffin@google.com \
    --cc=vdye@github.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).