Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] SubmittingPatches: separate typofixes section
Date: Tue, 02 Jun 2026 23:28:02 +0900	[thread overview]
Message-ID: <xmqqbjdtuidp.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD0ij4BTVTie1dXwTC8M_9gAvroXebFLmQuY7eUCgHrJhA@mail.gmail.com> (Christian Couder's message of "Tue, 2 Jun 2026 16:24:39 +0200")

Christian Couder <christian.couder@gmail.com> writes:

> On Tue, Jun 2, 2026 at 11:13 AM Junio C Hamano <gitster@pobox.com> 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.
>
> s/typofies/typofixes/
>
> Thanks.

Thanks.  It is amusing to see I cannot say typofixes when I talk
about them ;-)

  reply	other threads:[~2026-06-02 14:28 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 [this message]
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 ` [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

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=xmqqbjdtuidp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox