From: Kousik Sanagavarapu <five231003@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2023, #05; Tue, 25)
Date: Wed, 26 Jul 2023 08:11:13 +0530 [thread overview]
Message-ID: <ZMCHybvLPQ5_MVuR@five231003> (raw)
In-Reply-To: <xmqqzg3jhd8v.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> wrote:
> Nah, that is not worth it, as I've already done ! -> test_must_fail
> fix locally yesterday.
Oh, thanks.
next prev parent reply other threads:[~2023-07-26 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 20:57 What's cooking in git.git (Jul 2023, #05; Tue, 25) Junio C Hamano
2023-07-25 20:59 ` Junio C Hamano
2023-07-25 21:17 ` Kousik Sanagavarapu
2023-07-25 21:50 ` Junio C Hamano
2023-07-26 2:41 ` Kousik Sanagavarapu [this message]
2023-07-25 22:39 ` Taylor Blau
2023-07-25 23:59 ` Junio C Hamano
2023-07-26 13:11 ` Phillip Wood
2023-07-26 16:34 ` Junio C Hamano
2023-07-27 21:24 ` Linus Arver
2023-07-27 21:52 ` 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=ZMCHybvLPQ5_MVuR@five231003 \
--to=five231003@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).