From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/2] Small updates to SubmittingPatches
Date: Tue, 2 Jun 2026 23:43:02 +0900 [thread overview]
Message-ID: <20260602144304.3341000-1-gitster@pobox.com> (raw)
In-Reply-To: <20260602090808.87837-1-gitster@pobox.com>
Recently I gave some advice on how a cover letter should
try to sell the idea to widest possible audience, and then
I realized that we do not seem to teach how in our guides.
Here is a small series to do so.
In this round, a few typos have been corrected, and improvements are
made thanks to help from Christian, Stolee, and Patrick.
1/2: SubmittingPatches: separate typofixes section
2/2: SubmittingPatches: describe cover letter
Documentation/SubmittingPatches | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
--
2.54.0-591-g9032776dcc
next prev parent reply other threads:[~2026-06-02 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 9:08 [PATCH 0/2] Small updates to SubmittingPatches Junio C Hamano
2026-06-02 9:08 ` [PATCH 1/2] SubmittingPatches: separate typofixes section Junio C Hamano
2026-06-02 14:24 ` Christian Couder
2026-06-02 14:28 ` Junio C Hamano
2026-06-02 15:16 ` Christian Couder
2026-06-02 14:46 ` Kristoffer Haugsbakk
2026-06-02 9:08 ` [PATCH 2/2] SubmittingPatches: describe cover letter Junio C Hamano
2026-06-02 12:07 ` Patrick Steinhardt
2026-06-02 13:36 ` Junio C Hamano
2026-06-02 12:29 ` Derrick Stolee
2026-06-02 13:43 ` Junio C Hamano
2026-06-02 14:43 ` Junio C Hamano [this message]
2026-06-02 14:43 ` [PATCH v2 1/2] SubmittingPatches: separate typofixes section Junio C Hamano
2026-06-02 14:43 ` [PATCH v2 2/2] SubmittingPatches: describe cover letter Junio C Hamano
2026-06-02 15:24 ` [PATCH v2 0/2] Small updates to SubmittingPatches Derrick Stolee
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=20260602144304.3341000-1-gitster@pobox.com \
--to=gitster@pobox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox