From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: fdm: add MANUAL file.
Date: Tue, 05 Sep 2023 21:26:06 +0200 [thread overview]
Message-ID: <20230905192606.kzjNUAby3xT-H8nYN8_Vfgs-YrfPplgbt4VvTGqx-fk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45850@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
There's a merged pull request on the void-packages repository
fdm: add MANUAL file.
https://github.com/void-linux/void-packages/pull/45850
Description:
Most of the documentation for this program are in the plaintext MANUAL file. If we're including the examples, the MANUAL is just as helpful to have around if not more so.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
prev parent reply other threads:[~2023-09-05 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 18:12 [PR PATCH] " non-Jedi
2023-09-05 19:26 ` leahneukirchen [this message]
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=20230905192606.kzjNUAby3xT-H8nYN8_Vfgs-YrfPplgbt4VvTGqx-fk@z \
--to=leahneukirchen@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).