From: Taylor Blau <me@ttaylorr.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Makefile: add help target
Date: Fri, 8 Apr 2022 11:30:14 -0400 [thread overview]
Message-ID: <YlBVBlwNVc8mEjn5@nand.local> (raw)
In-Reply-To: <20220408074524.156165-1-gitter.spiros@gmail.com>
On Fri, Apr 08, 2022 at 07:45:24AM +0000, Elia Pinto wrote:
> Add a help target to the Makefile to be able to run make help, in the same way
> does the Makefiles self-generated by some build systems.
>
> The target list has been statically extracted from the git Makefile with a
> script and the results have been filtered in an essentially arbitrary way to
> leave the ones that i imagines most interesting and frequent for a developer.
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.
I worry about this list getting stale, though. If we add a new target,
will we remember to update the "help" list here? It would be nice if we
could dynamically generate this list, but I think that loses out on the
filtering you've done here.
Thanks,
Taylor
next prev parent reply other threads:[~2022-04-08 15:30 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 [this message]
2022-04-08 15:44 ` Ævar Arnfjörð Bjarmason
2022-04-08 18:58 ` Junio C Hamano
-- 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=YlBVBlwNVc8mEjn5@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.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).