From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: Re: What's cooking in git.git (Jun 2021, #03; Tue, 8)
Date: Tue, 08 Jun 2021 14:25:54 +0200 [thread overview]
Message-ID: <87r1hc35f8.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqeeddq7h5.fsf@gitster.g>
On Tue, Jun 08 2021, Junio C Hamano wrote:
> [New Topics]
Missing here is Jiang Xin's 2-patch series to fix a portability issue
with the "git bundle" tests:
https://lore.kernel.org/git/20210601144901.31375-1-worldhello.net@gmail.com/
It looks good to me, and it would be good to have it picked up for
merging to master sooner than later, as it's a rather isolated fix for a
portability issues in the tests.
If it helps consider it to have my:
Reviewed-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
next prev parent reply other threads:[~2021-06-08 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 4:57 What's cooking in git.git (Jun 2021, #03; Tue, 8) Junio C Hamano
2021-06-08 12:25 ` Ævar Arnfjörð Bjarmason [this message]
2021-06-08 23:18 ` Junio C Hamano
2021-06-09 9:26 ` Jiang Xin
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=87r1hc35f8.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@gmail.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).