From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"brian m . carlson" <sandals@crustytoothpaste.net>,
"Martin Ågren" <martin.agren@gmail.com>,
"Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: [PATCH v2 0/5] doc: asciidoc cleanups
Date: Fri, 14 May 2021 06:56:26 -0500 [thread overview]
Message-ID: <20210514115631.503276-1-felipe.contreras@gmail.com> (raw)
This patch series is an attempt to cleanup the Makefile of the documentation.
It's quie different from v1 mainly because now the .DELETE_ON_ERROR approach is being used as Aevar
suggested, however it tries to do the same thing.
It does not enable asciidoctor direct man page creation, that's in a separate patch.
Felipe Contreras (5):
doc: refactor common asciidoc dependencies
doc: improve asciidoc dependencies
doc: remove unnecessary rm instances
doc: simplify Makefile using .DELETE_ON_ERROR
doc: avoid using rm directly
Documentation/Makefile | 77 ++++++++++++++++--------------------------
1 file changed, 29 insertions(+), 48 deletions(-)
Range-diff against v1:
1: 62d76c126a < -: ---------- doc: standardize asciidoc calls
2: 0677725926 < -: ---------- doc: add an asciidoc helper
3: ca69c75596 < -: ---------- doc: disable asciidoc-helper for asciidoctor
4: f379515577 < -: ---------- doc: simplify the handling of interruptions
5: d2d10b34f3 < -: ---------- doc: remove redundant rm
6: d78e08aa2a < -: ---------- doc: refactor common dependencies
7: 450a79d36f < -: ---------- doc: improve asciidoc dependencies
8: 5be9efaa11 < -: ---------- doc: join xml and man rules
-: ---------- > 1: 55b188c8ad doc: refactor common asciidoc dependencies
-: ---------- > 2: e69d0a5b89 doc: improve asciidoc dependencies
-: ---------- > 3: 4f18675ce9 doc: remove unnecessary rm instances
-: ---------- > 4: 935675e070 doc: simplify Makefile using .DELETE_ON_ERROR
-: ---------- > 5: b621f3b8e9 doc: avoid using rm directly
--
2.31.1
next reply other threads:[~2021-05-14 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 11:56 Felipe Contreras [this message]
2021-05-14 11:56 ` [PATCH v2 1/5] doc: refactor common asciidoc dependencies Felipe Contreras
2021-05-14 11:56 ` [PATCH v2 2/5] doc: improve " Felipe Contreras
2021-05-14 11:56 ` [PATCH v2 3/5] doc: remove unnecessary rm instances Felipe Contreras
2021-05-15 9:24 ` Jeff King
2021-05-15 12:04 ` Felipe Contreras
2021-05-17 8:53 ` Jeff King
2021-05-17 10:42 ` Felipe Contreras
2021-05-17 11:40 ` Jeff King
2021-05-14 11:56 ` [PATCH v2 4/5] doc: simplify Makefile using .DELETE_ON_ERROR Felipe Contreras
2021-05-14 11:56 ` [PATCH v2 5/5] doc: avoid using rm directly 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210514115631.503276-1-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).