From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2023, #07; Mon, 30)
Date: Mon, 30 Jan 2023 15:27:06 -0800 [thread overview]
Message-ID: <xmqqa61z1u45.fsf@gitster.g> (raw)
In-Reply-To: <xmqqedrb1uvy.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 30 Jan 2023 15:10:25 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Subject: Re: What's cooking in git.git (Jan 2023, #07; Mon, 30)
Sorry, but this is the 8th issue of the month, not the 7th.
next prev parent reply other threads:[~2023-01-30 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 23:10 What's cooking in git.git (Jan 2023, #07; Mon, 30) Junio C Hamano
2023-01-30 23:27 ` Junio C Hamano [this message]
2023-01-31 12:42 ` 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=xmqqa61z1u45.fsf@gitster.g \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.