From: Taylor Blau <firstname.lastname@example.org>
To: "Ævar Arnfjörð Bjarmason" <email@example.com>
Cc: Taylor Blau <firstname.lastname@example.org>, email@example.com
Subject: Re: ab/misc-hook-submodule-run-command (was: What's cooking in git.git (Oct 2022, #09; Mon, 31))
Date: Mon, 31 Oct 2022 20:15:39 -0400 [thread overview]
Message-ID: <Y2BlK5uhCy77Ot4Z@nand.local> (raw)
On Tue, Nov 01, 2022 at 12:46:57AM +0100, Ævar Arnfjörð Bjarmason wrote:
> On Mon, Oct 31 2022, Taylor Blau wrote:
> > * ab/misc-hook-submodule-run-command (2022-10-31) 3 commits
> > - run-command tests: test stdout of run_command_parallel()
> > - submodule tests: reset "trace.out" between "grep" invocations
> > - hook tests: fix redirection logic error in 96e7225b310
> > Various test updates.
> > Waiting for review.
> > source: <cover-0.3-00000000000-20221029T025520Zfirstname.lastname@example.org>
> I think per
> that this is ready to advance.
Yeah, I agree. I was mistaken that GIT_TRACE truncated its output when
redirected to a file, but it appends. So, the series looks fine to me.
I would still like to hear from Emily, but otherwise I don't have a
problem starting to merge this down.
next prev parent reply other threads:[~2022-11-01 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 5:31 What's cooking in git.git (Oct 2022, #09; Mon, 31) Taylor Blau
2022-10-31 23:44 ` ab/cmake-nix-and-ci (was: What's cooking in git.git (Oct 2022, #09; Mon, 31)) Ævar Arnfjörð Bjarmason
2022-10-31 23:45 ` ab/make-bin-wrappers " Ævar Arnfjörð Bjarmason
2022-10-31 23:46 ` ab/misc-hook-submodule-run-command " Ævar Arnfjörð Bjarmason
2022-11-01 0:15 ` Taylor Blau [this message]
2022-11-02 17:13 ` Ævar Arnfjörð Bjarmason
2022-11-02 17:24 ` Taylor Blau
2022-11-02 16:49 ` What's cooking in git.git (Oct 2022, #09; Mon, 31) Ramsay Jones
2022-11-02 17:22 ` js/bisect-in-c (was: What's cooking in git.git (Oct 2022, #09; Mon, 31)) Ævar Arnfjörð Bjarmason
2022-11-02 17:26 ` Taylor Blau
2022-11-10 13:35 ` Johannes Schindelin
2022-11-11 4:46 ` Taylor Blau
2022-11-11 14:11 ` Ævar Arnfjörð Bjarmason
2022-11-10 13:32 ` Johannes Schindelin
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).