From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tomas Volf <~@wolfsden.cz>
Cc: 71800@debbugs.gnu.org
Subject: bug#71800: [PATCH 0/2] Improve documentation about using modules.
Date: Mon, 01 Jul 2024 23:31:28 -0400 [thread overview]
Message-ID: <87o77g5v1r.fsf@gmail.com> (raw)
In-Reply-To: <20240627141716.30583-1-~@wolfsden.cz> (Tomas Volf's message of "Thu, 27 Jun 2024 16:17:16 +0200")
Hi Tomas!
Tomas Volf <~@wolfsden.cz> writes:
> Document the #:hide argument. Correct text for implication of leaving
> all optional arguments out.
>
> Tomas Volf (2):
> doc: Document #:hide.
> doc: Fix implication of omitting optional arguments.
>
This looks good to me.
Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail>
--
Thanks,
Maxim
prev parent reply other threads:[~2024-07-02 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 14:17 bug#71800: [PATCH 0/2] Improve documentation about using modules Tomas Volf
2024-06-27 14:18 ` bug#71800: [PATCH 1/2] doc: Document #:hide Tomas Volf
2024-06-27 14:18 ` bug#71800: [PATCH 2/2] doc: Fix implication of omitting optional arguments Tomas Volf
2024-07-02 3:31 ` Maxim Cournoyer [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o77g5v1r.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71800@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).