git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: ab/make-dependency (was: What's cooking in git.git (Dec 2021, #04; Wed, 15))
Date: Fri, 17 Dec 2021 00:46:46 +0100	[thread overview]
Message-ID: <211217.86a6h09km9.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq8rwlz3cq.fsf@gitster.g>


On Wed, Dec 15 2021, Junio C Hamano wrote:

> * ab/make-dependency (2021-11-18) 24 commits
>  - Makefile: move ".SUFFIXES" rule to shared.mak
>  - Makefile: define $(LIB_H) in terms of $(FIND_SOURCE_FILES)
>  - Makefile: disable GNU make built-in wildcard rules
>  - Makefile: use $(file) I/O instead of "FORCE" when possible
>  - Makefile: correct the dependency graph of hook-list.h
>  - Makefiles: add and use wildcard "mkdir -p" template
>  - Makefile: use $(wspfx) for $(QUIET...) in shared.mak
>  - Makefile: add "$(QUIET)" boilerplate to shared.mak
>  - Makefile: add a "TRACK_template" for GIT-*{FLAGS,DEFINES,...}
>  - Makefile: re-add and use the "shellquote" macros
>  - Makefile: move $(comma), $(empty) and $(space) to shared.mak
>  - Makefiles: add "shared.mak", move ".DELETE_ON_ERROR" to it
>  - Makefile: stop needing @@GIT_VERSION@@ in *.perl scripts
>  - Makefile: create a GIT-PYTHON-DEFINES, like "PERL"
>  - Makefile: correct "GIT-PERL-{DEFINES,HEADER}" dependency graph
>  - Makefile: adjust Perl-related comments & whitespace
>  - Makefile: change "ifndef NO_PERL" to "ifdef NO_PERL"
>  - Makefile: guard Perl-only variable assignments
>  - Makefile: remove "mv $@ $@+" dance redundant to .DELETE_ON_ERROR
>  - Makefile: clean perl/build/ even with NO_PERL=Y
>  - Makefile: use "=" not ":=" for po/* and perl/*
>  - Makefile: don't set up "perl/build" rules under NO_PERL=Y
>  - Makefile: don't invoke msgfmt with --statistics
>  - Merge branch 'ab/sh-retire-helper-functions' into ab/make-dependency
>
>  Dependency clean-up.
>
>  Needs review.
>  There are some comments on earlier rounds; the latest one needs a
>  serious review or at least Acks from past commentors.
>  source: <patch-v4-23.23-48a3927d972-20211117T101807Z-avarab@gmail.com>

I think it's best to drop this rather large topic for now.

I started re-rolling it with improvements to address your shell escaping
comments, and ended up with a much better end-state, but it's now at
north of 30 commits locally.

So I've split it up and have some incoming patches. Not for all of it,
just starting with some of the more urgent than not fixes & more trivial
& easy to review changes, or around 1/2 of what's quoted above.

I'll then submit the rest sometime after that lands.


  parent reply	other threads:[~2021-12-16 23:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16  2:32 What's cooking in git.git (Dec 2021, #04; Wed, 15) Junio C Hamano
2021-12-16 11:51 ` ab/run-command (was: What's cooking in git.git (Dec 2021, #04; Wed, 15)) Ævar Arnfjörð Bjarmason
2021-12-16 15:31   ` Jeff King
2021-12-16 15:38     ` Ævar Arnfjörð Bjarmason
2021-12-16 19:11       ` ab/run-command Junio C Hamano
2022-04-06 10:42     ` [PATCH 0/3] run-command.h: rename "env_array" to "env" Ævar Arnfjörð Bjarmason
2022-04-06 10:42       ` [PATCH 1/3] cocci: add a rename of "struct child_process"'s " Ævar Arnfjörð Bjarmason
2022-04-06 10:42       ` [PATCH 2/3] run-command API: rename " Ævar Arnfjörð Bjarmason
2022-04-06 10:42       ` [PATCH 3/3] run-command API users: use "env" not "env_array" in comments & names Ævar Arnfjörð Bjarmason
2022-04-07 12:09       ` [PATCH 0/3] run-command.h: rename "env_array" to "env" Johannes Schindelin
2022-04-07 16:48         ` Junio C Hamano
2022-04-07 17:52           ` Junio C Hamano
2022-05-20  7:24       ` [PATCH v2 0/4] " Ævar Arnfjörð Bjarmason
2022-05-20  7:24         ` [PATCH v2 1/4] cocci: add a rename of "struct child_process"'s " Ævar Arnfjörð Bjarmason
2022-05-20  7:24         ` [PATCH v2 2/4] run-command API: rename " Ævar Arnfjörð Bjarmason
2022-05-20  7:24         ` [PATCH v2 3/4] cocci: remove env_array -> env migration Ævar Arnfjörð Bjarmason
2022-05-20  7:24         ` [PATCH v2 4/4] run-command API users: use "env" not "env_array" in comments & names Ævar Arnfjörð Bjarmason
2022-05-20 16:27         ` [PATCH v2 0/4] run-command.h: rename "env_array" to "env" Junio C Hamano
2022-05-21 11:09           ` Ævar Arnfjörð Bjarmason
2022-06-02  9:09         ` [PATCH v3 0/2] " Ævar Arnfjörð Bjarmason
2022-06-02  9:09           ` [PATCH v3 1/2] run-command API: " Ævar Arnfjörð Bjarmason
2022-06-03  0:37             ` Junio C Hamano
2022-06-02  9:09           ` [PATCH v3 2/2] run-command API users: use "env" not "env_array" in comments & names Ævar Arnfjörð Bjarmason
2021-12-16 23:46 ` Ævar Arnfjörð Bjarmason [this message]
2021-12-21  1:34 ` What's cooking in git.git (Dec 2021, #04; Wed, 15) Aleen 徐沛文
2021-12-21  7:30   ` Christian Couder

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=211217.86a6h09km9.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).