From: Josef Bacik <josef@toxicpanda.com>
To: alx@kernel.org, linux-man@vger.kernel.org, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, mszeredi@redhat.com,
kernel-team@fb.com
Subject: [PATCH v4 0/2] man-pages: add documentation for statmount/listmount
Date: Mon, 1 Jul 2024 09:37:52 -0400 [thread overview]
Message-ID: <cover.1719840964.git.josef@toxicpanda.com> (raw)
V3: https://lore.kernel.org/linux-fsdevel/cover.1719425922.git.josef@toxicpanda.com/
V2: https://lore.kernel.org/linux-fsdevel/cover.1719417184.git.josef@toxicpanda.com/
V1: https://lore.kernel.org/linux-fsdevel/cover.1719341580.git.josef@toxicpanda.com/
v3->v4:
- Addressed review comments.
v2->v3:
- Removed a spurious \t comment in listmount.2 (took me a while to figure out
why it was needed in statmount.2 but not listmount.2, it's because it lets you
know that there's a TS in the manpage).
- Fixed some unbalanced " in both pages
- Removed a EE in the nf section which is apparently not needed
v1->v2:
- Dropped the statx patch as Alejandro already took it (thanks!)
- Reworked everything to use semantic newlines
- Addressed all of the comments on the statmount.2 man page
Managed to get more of the build system running so hopefully this is all
formatted properly now. Thanks,
Josef
Josef Bacik (2):
statmount.2: New page describing the statmount syscall
listmount.2: New page describing the listmount syscall
man/man2/listmount.2 | 111 +++++++++++++++++
man/man2/statmount.2 | 288 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 399 insertions(+)
create mode 100644 man/man2/listmount.2
create mode 100644 man/man2/statmount.2
--
2.43.0
next reply other threads:[~2024-07-01 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 13:37 Josef Bacik [this message]
2024-07-01 13:37 ` [PATCH v4 1/2] statmount.2: New page describing the statmount syscall Josef Bacik
2024-07-09 12:27 ` Alejandro Colomar
2024-07-01 13:37 ` [PATCH v4 2/2] listmount.2: New page describing the listmount syscall Josef Bacik
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.1719840964.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=alx@kernel.org \
--cc=brauner@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mszeredi@redhat.com \
/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).