From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: [PATCH 0/4] doc-diff: support diffing from/to AsciiDoc(tor)
Date: Sun, 17 Mar 2019 19:35:59 +0100 [thread overview]
Message-ID: <cover.1552838239.git.martin.agren@gmail.com> (raw)
I've taught `doc-diff` a few new knobs to support usage like
$ ./doc-diff --from-asciidoc --to-asciidoctor HEAD HEAD
and I don't think I've messed it up too badly in the process. I'm open
to the idea that this might not be interesting to a whole lot of people.
But I have made some progress on fixing up Asciidoctor *and* AsciiDoc
issues using this, and once the output of the above command is empty --
which might not be too far off -- it could be interesting to try and
keep it that way using a bit of automation around these switches.
While using/testing these patches, I've made some progress on the
rendering of the headers and footers in Asciidoctor [1], so the
`--cut-header-footer` switch that I'm adding in the final patch might
hopefully not be necessary for too long. But we'd still need a
`--cut-footer` switch -- at least I would, on my system [2]. If this
series is considered generally sane, I'd be happy to rework the final
patch to `--cut-header` if that's preferred.
Patch 1 has a minor purely-textual merge conflict with
ma/asciidoctor-fixes.
[1] https://public-inbox.org/git/20190317144747.2418514-1-martin.agren@gmail.com/
[2] After [1], the date in the footer is still formatted differently
here. It might be a locale thing, and I tend to shy away from even
trying to understand those. :-/
Martin Ågren (4):
Doc: auto-detect changed build flags
doc-diff: let `render_tree()` take an explicit directory name
doc-diff: support diffing from/to AsciiDoc(tor)
doc-diff: add `--cut-header-footer`
Documentation/.gitignore | 1 +
Documentation/Makefile | 23 ++++++++---
Documentation/doc-diff | 86 +++++++++++++++++++++++++++++++++-------
3 files changed, 90 insertions(+), 20 deletions(-)
--
2.21.0
next reply other threads:[~2019-03-17 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 18:35 Martin Ågren [this message]
2019-03-17 18:36 ` [PATCH 1/4] Doc: auto-detect changed build flags Martin Ågren
2019-03-17 18:36 ` [PATCH 2/4] doc-diff: let `render_tree()` take an explicit directory name Martin Ågren
2019-03-17 18:36 ` [PATCH 3/4] doc-diff: support diffing from/to AsciiDoc(tor) Martin Ågren
2019-03-17 18:36 ` [PATCH 4/4] doc-diff: add `--cut-header-footer` Martin Ågren
2019-03-18 6:53 ` [PATCH 0/4] doc-diff: support diffing from/to AsciiDoc(tor) Junio C Hamano
2019-03-19 3:14 ` Jeff King
2019-03-20 20:11 ` Martin Ågren
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=cover.1552838239.git.martin.agren@gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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.
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).