From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: ab/plug-leak-in-revisions
Date: Wed, 13 Apr 2022 16:32:28 -0700 [thread overview]
Message-ID: <xmqq35ig5zlf.fsf@gitster.g> (raw)
In-Reply-To: <220413.86bkx4eobr.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Wed, 13 Apr 2022 22:08:54 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> I think it should be ready with my just-submitted re-roll, which fixes a
> trivial nit spotted by Phillip Wood by removing a useless NULL check:
> https://lore.kernel.org/git/cover-v6-00.27-00000000000-20220413T195935Z-avarab@gmail.com/
Last time I checked, the last three patches haven't made to the lore
archive yet. We have other things to do while waiting for them, so
there is no need to rush or resend ;-)
next prev parent reply other threads:[~2022-04-13 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 17:04 What's cooking in git.git (Apr 2022, #03; Tue, 12) Junio C Hamano
2022-04-12 17:52 ` Philippe Blain
2022-04-12 18:55 ` CVE-2022-24765 and core.sharedRepository (was: What's cooking in git.git (Apr 2022, #03; Tue, 12)) Ævar Arnfjörð Bjarmason
2022-04-13 3:10 ` demerphq
2022-04-13 23:51 ` What's cooking in git.git (Apr 2022, #03; Tue, 12) Junio C Hamano
2022-04-13 20:08 ` ab/plug-leak-in-revisions (was: What's cooking in git.git (Apr 2022, #03; Tue, 12)) Ævar Arnfjörð Bjarmason
2022-04-13 23:32 ` Junio C Hamano [this message]
2022-04-14 7:22 ` ab/plug-leak-in-revisions Ævar Arnfjörð Bjarmason
2022-04-14 18:33 ` ab/plug-leak-in-revisions Junio C Hamano
2022-04-13 20:11 ` ab/ci-setup-simplify etc. (was: What's cooking in git.git (Apr 2022, #03; Tue, 12)) Ævar Arnfjörð Bjarmason
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=xmqq35ig5zlf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@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 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.