From: Florian Weimer <fweimer@redhat.com>
To: Jason Yundt <jason@jasonyundt.email>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH v4] man/man7/pathname.7: Add file documenting format of pathnames
Date: Wed, 15 Jan 2025 18:12:04 +0100 [thread overview]
Message-ID: <87y0zcgfx7.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20250115162052.131794-1-jason@jasonyundt.email> (Jason Yundt's message of "Wed, 15 Jan 2025 11:20:51 -0500")
* Jason Yundt:
> +.IP \[bu]
> +Filenames can be at most 255 bytes long.
I don't think this is accurate, particularly not for network file
systems and file systems that use UCS-2 or UTF-16 internally. The
latter typically have their own 255 character limit, but a character can
take up to 3 bytes in UTF-8 (as used by Linux).
This is why we deprecated readdir_r.
Thanks,
Florian
next prev parent reply other threads:[~2025-01-15 17:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 21:32 [PATCH] man/man7/path-format.7: Add file documenting format of pathnames Jason Yundt
2025-01-14 0:20 ` Alejandro Colomar
2025-01-14 12:54 ` [PATCH v2] " Jason Yundt
2025-01-14 13:14 ` Alejandro Colomar
2025-01-14 21:00 ` Jason Yundt
2025-01-14 23:06 ` Alejandro Colomar
2025-01-15 16:21 ` Jason Yundt
2025-01-15 16:47 ` Alejandro Colomar
2025-01-15 17:44 ` G. Branden Robinson
2025-01-15 9:01 ` Florian Weimer
2025-01-14 21:01 ` [PATCH v3] man/man7/path_format.7: " Jason Yundt
2025-01-15 16:20 ` [PATCH v4] man/man7/pathname.7: " Jason Yundt
2025-01-15 17:12 ` Florian Weimer [this message]
2025-01-15 17:20 ` Alejandro Colomar
2025-01-15 18:37 ` A modest proposal regarding pathnames (was: " G. Branden Robinson
2025-01-15 19:25 ` Alejandro Colomar
2025-01-15 19:47 ` Alejandro Colomar
2025-01-17 13:02 ` [PATCH v5] " Jason Yundt
2025-01-17 14:14 ` Alejandro Colomar
2025-01-18 0:01 ` Jason Yundt
2025-01-18 0:23 ` Alejandro Colomar
2025-01-19 13:17 ` Jason Yundt
2025-01-19 15:24 ` Alejandro Colomar
2025-01-20 8:20 ` Florian Weimer
2025-01-20 11:14 ` Alejandro Colomar
2025-01-20 13:17 ` Jason Yundt
2025-01-20 13:25 ` Alejandro Colomar
2025-01-17 23:59 ` [PATCH v6] " Jason Yundt
2025-01-20 16:24 ` [PATCH v8] " Jason Yundt
2025-01-20 16:36 ` Alejandro Colomar
2025-01-20 19:06 ` [PATCH v9] " Jason Yundt
2025-01-20 22:26 ` Alejandro Colomar
2025-01-21 0:26 ` C code style for Linux man-pages examples (was: [PATCH v9] man/man7/pathname.7: Add file documenting format of pathnames) G. Branden Robinson
2025-01-21 1:05 ` Alejandro Colomar
2025-01-21 13:39 ` Jason Yundt
2025-01-21 14:00 ` Alejandro Colomar
2025-01-21 13:35 ` [PATCH v10] man/man7/pathname.7: Add file documenting format of pathnames Jason Yundt
2025-01-23 23:51 ` 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=87y0zcgfx7.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alx@kernel.org \
--cc=jason@jasonyundt.email \
--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