From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Elia Pinto <gitter.spiros@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Makefile: add help target
Date: Fri, 08 Apr 2022 11:58:24 -0700 [thread overview]
Message-ID: <xmqq1qy7mmgf.fsf@gitster.g> (raw)
In-Reply-To: <YlBVBlwNVc8mEjn5@nand.local> (Taylor Blau's message of "Fri, 8 Apr 2022 11:30:14 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> I could definitely see something like "make help" being helpful, since
> make itself doesn't have a convenient way to list all of a Makefile's
> targets.
But is listing all useful to begin with? I doubt it.
Most useful targets are all .PHONYs, so a possible approach is to
make them double-colon rules, and have a section at the top, next to
where we explain "# The default target of this Makefile is...", that
lists all of them there, and have a rule
# The default target of this Makefile is...
all::
+# Common targets
+test::
+doc::
+...
+help::
+ sed -e '/help::/q' Makefile
# Import tree-wide shared Makefile behavior and libraries
include shared.mak
perhaps?
> I worry about this list getting stale, though.
Absolutely.
A well-curated list of common targets, maybe, but I find nothing
interesting in the posted patch that lists way too many.
I also suspect that a well-curated list at the top would eliminate
the need for the "help" target in the first place. Between "make
help" and "less Makefile", the latter is much more intuitive.
Thanks.
next prev parent reply other threads:[~2022-04-08 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 7:45 [PATCH] Makefile: add help target Elia Pinto
2022-04-08 9:32 ` Philip Oakley
2022-04-08 15:30 ` Taylor Blau
2022-04-08 15:44 ` Ævar Arnfjörð Bjarmason
2022-04-08 18:58 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 8:13 [PATCH] Makefile: Add " Stephen Boyd
2010-09-28 9:45 ` Junio C Hamano
2010-09-28 11:37 ` Sverre Rabbelier
2010-09-28 12:35 ` Andreas Ericsson
2010-09-29 6:10 ` yj2133011
2010-08-25 9:51 Stephen Boyd
2010-08-25 16:27 ` Sverre Rabbelier
2010-08-25 21:36 ` Stephen Boyd
2010-08-25 21:39 ` Sverre Rabbelier
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=xmqq1qy7mmgf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
--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.