From: xelxebar <xelxebar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: metamath-0.180
Date: Wed, 19 Aug 2020 02:21:28 +0200 [thread overview]
Message-ID: <20200819002128.2by6FjgQ9xTCVB2bxqM-UCBk8VWxwZZOyJFKCPrt1JQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18584@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
New comment by xelxebar on void-packages repository
https://github.com/void-linux/void-packages/pull/18584#issuecomment-675782023
Comment:
@ahesford Thanks for looking at this. That's reasonable stance. I am happy to remove the pdf if that will get this merged.
That said; the pdf really is the only reasonable local documentation. The man page just provides a terse overview of the internal metamath syntax, and the README only discusses details about building. Upstream's official documentation is the pdf, which is why I figured it makes sense to include it in the package.
Cheers!
next prev parent reply other threads:[~2020-08-19 0:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 15:20 [PR PATCH] New package: metamath-0.178 voidlinux-github
2020-01-27 15:26 ` voidlinux-github
2020-01-31 1:14 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-31 1:17 ` New package: metamath-0.180 voidlinux-github
2020-02-01 3:25 ` voidlinux-github
2020-02-02 15:37 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-04 13:08 ` voidlinux-github
2020-02-05 2:16 ` voidlinux-github
2020-04-23 7:16 ` [PR PATCH] [Updated] " xelxebar
2020-07-07 2:35 ` xelxebar
2020-07-07 2:58 ` [PR PATCH] [Updated] " xelxebar
2020-07-07 2:59 ` xelxebar
2020-07-07 3:03 ` xelxebar
2020-07-07 3:03 ` xelxebar
2020-07-07 4:17 ` ericonr
2020-07-07 4:44 ` [PR PATCH] [Updated] " xelxebar
2020-07-07 4:48 ` xelxebar
2020-08-18 19:17 ` ahesford
2020-08-19 0:21 ` xelxebar [this message]
2020-08-19 2:31 ` ahesford
2021-02-16 16:18 ` ericonr
2021-03-24 19:04 ` ericonr
2021-03-24 19:04 ` [PR PATCH] [Closed]: " ericonr
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=20200819002128.2by6FjgQ9xTCVB2bxqM-UCBk8VWxwZZOyJFKCPrt1JQ@z \
--to=xelxebar@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).