From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Bill O'Donnell <bodonnel@redhat.com>,
Eric Sandeen <sandeen@redhat.com>,
linux-fsdevel@vger.kernel.org,
David Howells <dhowells@redhat.com>,
Alexander Viro <aviro@redhat.com>,
Bill O'Donnell <billodo@redhat.com>, Karel Zak <kzak@redhat.com>
Subject: Re: [PATCH RFC] vfs: always log mount API fs context messages to dmesg
Date: Fri, 23 Feb 2024 17:58:45 -0800 [thread overview]
Message-ID: <20240224015845.GO6226@frogsfrogsfrogs> (raw)
In-Reply-To: <20240223-semmel-szenarien-cbf7b7599ac0@brauner>
On Fri, Feb 23, 2024 at 04:56:34PM +0100, Christian Brauner wrote:
> > Can we /please/ document and write (more) fstests for these things?
>
> So fstests I've written quite extensively for at least mount_setattr(2)
> and they're part of fstests/src/vfs/ and some other tests for other new
> api calls.
>
> A long time ago I got tired of writing groff (or whatever it's called),
> and it's tedious semantics and the involved upstreaming process. So a
> while ago I just started converting my manpages into markdown and
> started updating them and if people were interested in upstreaming this
> as groff then they're welcome. So:
>
> https://github.com/brauner/man-pages-md
>
> This also includes David's manpages which I had for a while locally but
> didn't convert. So I did that now.
Egad that's so much less fugly. Do you think we can convince Alejandro
to take some of that without so much demands of splitting things and
whatnot?
(Thanks for keeping those from bitrotting btw)
--D
next prev parent reply other threads:[~2024-02-24 1:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:22 [PATCH RFC] vfs: always log mount API fs context messages to dmesg Eric Sandeen
2024-02-22 15:58 ` Bill O'Donnell
2024-02-22 16:08 ` Darrick J. Wong
2024-02-23 15:56 ` Christian Brauner
2024-02-24 1:58 ` Darrick J. Wong [this message]
2024-02-26 10:51 ` Christian Brauner
2024-02-23 15:06 ` Christian Brauner
2024-02-23 16:27 ` Eric Sandeen
2024-02-26 11:21 ` Christian Brauner
2024-02-26 9:04 ` Karel Zak
2024-02-27 1:27 ` Kent Overstreet
2024-02-26 11:27 ` Christian Brauner
2024-02-26 15:23 ` Eric Sandeen
2024-02-27 1:21 ` Ian Kent
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=20240224015845.GO6226@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aviro@redhat.com \
--cc=billodo@redhat.com \
--cc=bodonnel@redhat.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@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).