From: Johnny Richard <johnny@johnnyrichard.com>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Johnny Richard <johnny@johnnyrichard.com>
Subject: [PATCH olang v1 0/3] docs: remove pandoc dependency
Date: Mon, 16 Sep 2024 18:29:11 +0200 [thread overview]
Message-ID: <20240916163004.43389-1-johnny@johnnyrichard.com> (raw)
Johnny Richard (3):
docs: move language spec to manual document
docs: stop using pandoc to generate page on website
docs: remove pandoc dependency for man docs
.build.yml | 1 -
docs/Makefile | 20 +++----
docs/index.html | 57 +++++++++++++++++++
docs/index.md | 20 -------
docs/manpages/olang.1 | 53 +++++++++++++++++
docs/manpages/olang.md | 40 -------------
docs/manual/Makefile | 2 +-
docs/manual/_header.html | 1 -
docs/manual/olang.texi | 3 +
.../specification.texi} | 13 ++---
docs/template.html | 31 ----------
11 files changed, 127 insertions(+), 114 deletions(-)
create mode 100644 docs/index.html
delete mode 100644 docs/index.md
create mode 100644 docs/manpages/olang.1
delete mode 100644 docs/manpages/olang.md
rename docs/{pages/language-specification.md => manual/specification.texi} (97%)
delete mode 100644 docs/template.html
base-commit: 3d4791adf7293e2f33d0dad1d3f426f33d690a6d
--
2.46.0
next reply other threads:[~2024-09-16 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 16:29 Johnny Richard [this message]
2024-09-16 14:32 ` Carlos Maniero
2024-09-16 16:29 ` [PATCH olang v1 1/3] docs: move language spec to manual document Johnny Richard
2024-09-16 16:29 ` [PATCH olang v1 2/3] docs: stop using pandoc to generate page on website Johnny Richard
2024-09-16 16:29 ` [PATCH olang v1 3/3] docs: remove pandoc dependency for man docs Johnny Richard
2024-09-16 14:31 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-09-16 16:37 ` [PATCH olang v1 0/3] docs: remove pandoc dependency Johnny Richard
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=20240916163004.43389-1-johnny@johnnyrichard.com \
--to=johnny@johnnyrichard.com \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/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://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox