From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: ab/make-bin-wrappers (was: What's cooking in git.git (Oct 2022, #09; Mon, 31))
Date: Tue, 01 Nov 2022 00:45:24 +0100 [thread overview]
Message-ID: <221101.86mt9b5zf3.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y19dnb2M+yObnftj@nand.local>
On Mon, Oct 31 2022, Taylor Blau wrote:
> * ab/make-bin-wrappers (2022-10-30) 3 commits
> - Makefile: simplify $(test_bindir_programs) rule by splitting it up
> - Makefile: define "TEST_{PROGRAM,OBJS}" variables earlier
> - Makefile: factor sed-powered '#!/bin/sh' munging into a variable
>
> Resolve issues with the bin-wrappers/% rules where "make
> bin-wrappers/git" would generate the script but not "git" itself.
>
> Waiting for review.
> source: <cover-v2-0.3-00000000000-20221026T143533Z-avarab@gmail.com>
I've since sent a v3, hopefully addressing outstanding feedback:
https://lore.kernel.org/git/cover-v3-0.4-00000000000-20221031T222249Z-avarab@gmail.com/
next prev parent reply other threads:[~2022-10-31 23:47 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 ` Ævar Arnfjörð Bjarmason [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=221101.86mt9b5zf3.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.
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.