From: Reuben Thomas <rrt@sc3d.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: NAME_MAX on MingW
Date: Mon, 8 Mar 2021 09:12:34 +0000 [thread overview]
Message-ID: <CAOnWdoiarmQx2isKhET0Mm6WLMdbUR+q5wUdQb4FnMjcLuc8SA@mail.gmail.com> (raw)
In-Reply-To: <1841389.BC9EOF7Wat@omega>
[-- Attachment #1: Type: text/plain, Size: 302 bytes --]
On Mon, 8 Mar 2021 at 00:14, Bruno Haible <bruno@clisp.org> wrote:
>
> I don't see anything Gnulib should do here.
>
Having looked into this, it seems that the same issues apply to PATH_MAX,
yet gnulib has a pathmax module to define PATH_MAX. What's different in
that case?
--
https://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 1032 bytes --]
next prev parent reply other threads:[~2021-03-08 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 23:22 NAME_MAX on MingW Reuben Thomas
2021-03-08 0:14 ` Bruno Haible
2021-03-08 0:16 ` Reuben Thomas
2021-03-08 9:24 ` Reuben Thomas
2021-03-08 10:06 ` Bruno Haible
2021-03-08 10:12 ` Reuben Thomas
2021-03-08 9:12 ` Reuben Thomas [this message]
2021-03-08 9:56 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOnWdoiarmQx2isKhET0Mm6WLMdbUR+q5wUdQb4FnMjcLuc8SA@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).