From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2024, #05; Thu, 12)
Date: Fri, 13 Dec 2024 06:48:14 -0800 [thread overview]
Message-ID: <xmqqfrmrbpw1.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD0mizHEAjW6A86-Ndp-h2RySQU+18oL-5fG9Ni_S70ycw@mail.gmail.com> (Christian Couder's message of "Fri, 13 Dec 2024 15:40:57 +0100")
Christian Couder <christian.couder@gmail.com> writes:
> A few typo fix suggestions:
Thanks. Very much appreciated.
next prev parent reply other threads:[~2024-12-13 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 12:31 What's cooking in git.git (Dec 2024, #05; Thu, 12) Junio C Hamano
2024-12-12 14:27 ` karthik nayak
2024-12-13 14:33 ` Junio C Hamano
2024-12-13 17:28 ` karthik nayak
2024-12-13 14:40 ` Christian Couder
2024-12-13 14:48 ` Junio C Hamano [this message]
2024-12-16 8:11 ` Patrick Steinhardt
2024-12-16 16:26 ` Junio C Hamano
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=xmqqfrmrbpw1.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;
as well as URLs for NNTP newsgroup(s).