From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] man/man2/statmount.2: Document STATMOUNT_BY_FD
Date: Thu, 5 Mar 2026 16:55:23 -0600 [thread overview]
Message-ID: <20260305225523.dh3ifjwkvvecv26c@illithid> (raw)
In-Reply-To: <aaoGRLXhJfpUz04o@devuan>
[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]
Hi Alex,
At 2026-03-05T23:45:14+0100, Alejandro Colomar wrote:
> On 2026-03-05T16:24:31-0600, G. Branden Robinson wrote:
> > [CC list trimmed way down since this is a *roff/formatting issue]
> >
> > Hi Alex,
> >
> > At 2026-03-05T18:19:30+0100, Alejandro Colomar wrote:
> > > BTW, Branden, I'm getting a diagnostic from groff:
> > >
> > > TROFF .tmp/man/man2/statmount.2.pdf.set
> > > ! (troff -mandoc -Tpdf -wbreak -rS12 -rU0 <.tmp/man/man2/statmount.2.pdf.troff 2>&1 >.tmp/man/man2/statmount.2.pdf.set) \
> > > | grep ^ >&2
> > > .tmp/man/man2/statmount.2:155: warning: table row does not fit on page 2
> > >
> > > But the PDF looks good to me. Would you mind looking at that page and
> > > telling me what you'd do with that diagnostic, and whether I should care
> > > about it?
> >
> > I can't reproduce this diagnostic with groff 1.23.0 or 1.24.0.
>
> Huh... I'm reproducing it on my server, but not on my desktop.
> On my server, I have:
>
> GNU troff (groff) version 1.23.0.1254-19a18
>
> On my desktop, I have:
>
> GNU grops (groff) version 1.23.0.2695-49927
Hmm. Revision 19a18 is 9 May 2024, and 49927 is 22 December 2024.
Both are a little old. :)
> I'll assume this is a fixed issue, since the newer groff(1) from my
> desktop doesn't reproduce it.
If I get stuck on the other stuff I'm working on,[1] I'll see if I can
reproduce the problem with 1.23.0.1254-19a18 and then bisect it down.
> > > .tmp/man/man2/statmount.2:155: warning: table row does not fit on page 2
> >
> > This warning means that a row of the table might be vertically
> > encroaching into the footer margin; in extreme cases, might
> > overprint the page footer itself; and in really loony cases, format
> > text beyond the bottom of the page.
>
> Yeah, that's what I was expecting, but the page renders fine, and I
> don't see anything near the margins, which made it weird.
The warning will issue if the table row is overset by as little as 1
"basic unit", which for PostScript and PDF is 1/72,000 of an inch.
That's 0.0000353 centimeters. It's microscopically small.
If there's a way to get the _amount_ of overset into that diagnostic
message, it would be helpful to the document maintainer to decide
whether it's a problem they want to deal with.
Your other data explains why I couldn't reproduce it. It could have
been a bug that got squashed between May and December of 2024.
If I find out it's still there, latent, I'll go at it with guns blazing.
Regards,
Branden
[1] largely https://savannah.gnu.org/bugs/?67978
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-05 22:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 14:45 [PATCH v2 00/10] man/man2/statmount.2: Document New Features Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 01/10] man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 02/10] man/man2/statmount.2: Document STATMOUNT_MNT_OPTS Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 03/10] man/man2/statmount.2: Document STATMOUNT_FS_SUBTYPE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 04/10] man/man2/statmount.2: Document STATMOUNT_SB_SOURCE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 05/10] man/man2/statmount.2: Document STATMOUNT_OPT_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 06/10] man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 07/10] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 08/10] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 09/10] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-22 14:46 ` [PATCH v2 10/10] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-22 21:52 ` [PATCH v2 00/10] man/man2/statmount.2: Document New Features Alejandro Colomar
2026-02-23 14:10 ` [PATCH v2 1/4] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-23 15:41 ` Alejandro Colomar
2026-02-23 18:17 ` [PATCH v2] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-24 0:21 ` Alejandro Colomar
2026-02-26 3:10 ` [PATCH v3] " Bhavik Sachdev
2026-03-04 14:58 ` Alejandro Colomar
2026-03-05 0:13 ` Askar Safin
2026-03-05 0:42 ` Alejandro Colomar
2026-03-05 2:18 ` Aleksa Sarai
2026-03-05 17:19 ` Alejandro Colomar
2026-03-05 22:24 ` G. Branden Robinson
2026-03-05 22:45 ` Alejandro Colomar
2026-03-05 22:55 ` G. Branden Robinson [this message]
2026-03-06 7:51 ` Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 2/4] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 3/4] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-23 14:10 ` [PATCH v2 4/4] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
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=20260305225523.dh3ifjwkvvecv26c@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox