From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [PATCH 1/2] SubmittingPatches: separate typofixes section
Date: Tue, 02 Jun 2026 16:46:05 +0200 [thread overview]
Message-ID: <c64bb761-a412-4ec5-a1b5-30f0893a3d1f@app.fastmail.com> (raw)
In-Reply-To: <20260602090808.87837-2-gitster@pobox.com>
On Tue, Jun 2, 2026, at 11:08, Junio C Hamano wrote:
> The existing text said something about tests (with [[tests]] to make
> it easier to refer to it from elsewhere) and then flowed into a
> different topic of typofixes, but it was unclear where the latter
> started. Add a similar [[typofies]] marker to the document.
>
> Signed-off-by: Junio C Hamano <gitster@pobox•com>
> ---
Imperative mood?
next prev parent reply other threads:[~2026-06-02 14:46 UTC|newest]
Thread overview: 16+ 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 [this message]
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 ` [PATCH v2 0/2] Small updates to SubmittingPatches Junio C Hamano
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
2026-06-04 6:50 ` Patrick Steinhardt
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=c64bb761-a412-4ec5-a1b5-30f0893a3d1f@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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