From: Felipe Contreras <firstname.lastname@example.org> To: Jeff King <email@example.com>, Felipe Contreras <firstname.lastname@example.org> Cc: email@example.com, "Martin Ågren" <firstname.lastname@example.org>, "brian m . carlson" <email@example.com>, "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Subject: Re: [PATCH 01/11] doc: allow the user to provide ASCIIDOC_EXTRA Date: Mon, 17 May 2021 05:53:25 -0500 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <YKIwDTQI3sBXu+7W@coredump.intra.peff.net> Jeff King wrote: > On Sat, May 15, 2021 at 07:13:48AM -0500, Felipe Contreras wrote: > > Jeff King wrote: > > > To go into further detail: usually we distinguish variables we use > > > internally from user-facing ones, and include the latter in the former. > > > I see a later patch wants to start passing ASCIIDOC_EXTRA on the > > > command-line, and we'd use two variables for that. > > > > Well, it's not exactly user-facing; it's only needed for doc-diff. > > It's meant for the caller of "make". Your proposed use is within > doc-diff, but any user running "make ASCIIDOC_EXTRA=foo" would see the > different behavior. Yeah, they would, but I don't think it would be wrong behavior. > > Would TEST_ASCIIDOC_EXTRA make sense? > > I'd probably call it ASCIIDOC_FLAGS (like we have CFLAGS and LDFLAGS > that are meant for users to inform us of extra flags they'd like > passed). Right, but Makefiles do override those, like: override CFLAGS += -fPIC Otherwise builds may fail. > Of course that may not solve your problem in a sense; if you want > doc-diff to override it, then that might conflict with a theoretical > ASCIIDOC_FLAGS somebody set in their config.mak (but we really are in > the realm of hypothetical here). Setting ASCIIDOC_FLAGS in config.mk would not override the user-supplied flags any more than setting them in the Makefile (they are virtually the same thing as one includes the other). It's only if the user has `override ASCIIDOC_FLAGS` in config.mk that such a problem would arise. And that's really hypothetical. Cheers. -- Felipe Contreras
next prev parent reply other threads:[~2021-05-17 10:53 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-14 12:14 [PATCH 00/11] doc: asciidoctor: direct man page creation and fixes Felipe Contreras 2021-05-14 12:14 ` [PATCH 01/11] doc: allow the user to provide ASCIIDOC_EXTRA Felipe Contreras 2021-05-15 9:32 ` Jeff King 2021-05-15 9:39 ` Jeff King 2021-05-15 12:13 ` Felipe Contreras 2021-05-17 8:57 ` Jeff King 2021-05-17 10:53 ` Felipe Contreras [this message] 2021-05-17 11:39 ` Jeff King 2021-05-17 16:50 ` Felipe Contreras 2021-05-14 12:14 ` [PATCH 02/11] doc: doc-diff: allow more than one flag Felipe Contreras 2021-05-15 9:37 ` Jeff King 2021-05-15 12:11 ` Felipe Contreras 2021-05-14 12:14 ` [PATCH 03/11] doc: doc-diff: set docdate manually Felipe Contreras 2021-05-14 15:43 ` Martin Ågren 2021-05-14 20:33 ` Felipe Contreras 2021-05-14 12:14 ` [PATCH 04/11] doc: use asciidoctor to build man pages directly Felipe Contreras 2021-05-14 15:38 ` Martin Ågren 2021-05-14 20:26 ` Felipe Contreras 2021-05-14 12:14 ` [PATCH 05/11] doc: asciidoctor: add linkgit macros in man pages Felipe Contreras 2021-05-14 12:14 ` [PATCH 06/11] doc: join mansource and manversion Felipe Contreras 2021-05-14 12:14 ` [PATCH 07/11] doc: add man pages workaround for asciidoctor Felipe Contreras 2021-05-14 12:14 ` [PATCH 08/11] doc: asciidoctor: add hack for xrefs Felipe Contreras 2021-05-14 12:14 ` [PATCH 09/11] doc: asciidoctor: add hack to improve links Felipe Contreras 2021-05-14 12:14 ` [PATCH 10/11] doc: asciidoctor: add support for baseurl Felipe Contreras 2021-05-14 12:14 ` [PATCH 11/11] doc: asciidoctor: cleanup man page hack Felipe Contreras
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 01/11] doc: allow the user to provide ASCIIDOC_EXTRA' \ /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
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).