All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-man@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: quotactl(2) (was: [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls)
Date: Fri, 11 Sep 2026 00:38:23 +0200	[thread overview]
Message-ID: <aqMwVislUcWIRTUb@devuan> (raw)
In-Reply-To: <aqLfs-6crlKiqZw9@devuan>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

[CC trimmed]

Hi Darrick,

> > Date: 2026-09-10 09:44:28-0700
> > From: "Darrick J. Wong" <djwong@kernel.org>
> >
> > quotactl (and xattrs) have a similar weird history of originating in XFS
> > and later getting yanked into the vfs.  Every time I have to go look up
> > the quota syscalls I just get a headache. :/

I have recently worked on having quotactl(2) split into more organized
manual pages.  This has been part of the man-pages-6.19 release.
Have you had a look at these manual pages after that change?  Did the
headache experience improve (or worsen) after this change?

Michael's man7.org already includes the latest version:
<https://www.man7.org/linux/man-pages/man2/quotactl.2.html>

I'd welcome feedback, and any improvements or suggestions to improve
the pages.


Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-09-10 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 10:41 [PATCH v2] man/man2: introduce man page for file_getattr/file_setattr syscalls Andrey Albershteyn
2026-09-10 13:20 ` Alejandro Colomar
2026-09-10 16:12   ` Darrick J. Wong
2026-09-10 16:31     ` Alejandro Colomar
2026-09-10 16:44       ` Darrick J. Wong
2026-09-10 16:50         ` Alejandro Colomar
2026-09-10 22:38           ` Alejandro Colomar [this message]
2026-09-11 11:17   ` Andrey Albershteyn
2026-09-11 11:56     ` Alejandro Colomar

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=aqMwVislUcWIRTUb@devuan \
    --to=alx@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.