From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: ab/misc-hook-submodule-run-command (was: What's cooking in git.git (Oct 2022, #09; Mon, 31))
Date: Wed, 02 Nov 2022 18:13:51 +0100 [thread overview]
Message-ID: <221102.86h6zh2rxf.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y2BlK5uhCy77Ot4Z@nand.local>
On Mon, Oct 31 2022, Taylor Blau wrote:
> 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-20221029T025520Z-avarab@gmail.com>
>>
>> I think per
>> https://lore.kernel.org/git/221031.86tu3k6u2d.gmgdl@evledraar.gmail.com/
>> &
>> https://lore.kernel.org/git/221031.86pme86tcg.gmgdl@evledraar.gmail.com/
>> 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.
(Just looking at what I can & can't unblock)
In case that's a "let's hear from the author" (understandable) then this
is entirely my work, even if it's her in the "author" header.
Her last version of tha commit was[1], but this entire test is from
my[2] re-roll of that topic[3].
1. https://lore.kernel.org/git/20210527000856.695702-8-emilyshaffer@google.com/
2. https://lore.kernel.org/git/patch-03.31-1ad4e69f7da-20210528T110515Z-avarab@gmail.com/
3. https://lore.kernel.org/git/cover-00.31-00000000000-20210528T110515Z-avarab@gmail.com/
next prev parent reply other threads:[~2022-11-02 17:21 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
2022-11-02 17:13 ` Ævar Arnfjörð Bjarmason [this message]
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
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
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 \
--in-reply-to=221102.86h6zh2rxf.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).