From: Joseph Myers <joseph@codesourcery.com>
To: DJ Delorie <dj@redhat.com>
Cc: fweimer@redhat.com, libc-alpha@sourceware.org
Subject: Re: [v2] nsswitch: do not reload if "/" changes
Date: Thu, 28 Jan 2021 00:39:24 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2101280038500.18505@digraph.polyomino.org.uk> (raw)
In-Reply-To: <xnlfcdhpap.fsf@greed.delorie.com>
On Thu, 28 Jan 2021, DJ Delorie wrote:
> What's the right macro for Hurd then?
Hurd does not have a limit on path length, but some tests do e.g.
#ifndef PATH_MAX
# define PATH_MAX 4096
#endif
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-01-28 0:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 0:59 nsswitch: do not reload if "/" changes DJ Delorie via Libc-alpha
2021-01-16 10:52 ` Florian Weimer via Libc-alpha
2021-01-18 1:13 ` DJ Delorie via Libc-alpha
2021-01-18 10:47 ` Florian Weimer via Libc-alpha
2021-01-18 18:20 ` DJ Delorie via Libc-alpha
2021-01-19 16:37 ` Florian Weimer via Libc-alpha
2021-01-22 19:10 ` [v2] " DJ Delorie via Libc-alpha
2021-01-26 9:58 ` Florian Weimer via Libc-alpha
2021-01-26 16:19 ` DJ Delorie via Libc-alpha
2021-01-26 16:30 ` Florian Weimer via Libc-alpha
2021-01-26 16:47 ` DJ Delorie via Libc-alpha
2021-01-27 17:28 ` Carlos O'Donell via Libc-alpha
2021-01-27 18:44 ` DJ Delorie via Libc-alpha
2021-01-28 0:31 ` Joseph Myers
2021-01-28 0:34 ` DJ Delorie via Libc-alpha
2021-01-28 0:39 ` Joseph Myers [this message]
2021-01-28 1:15 ` DJ Delorie via Libc-alpha
2021-01-18 12:42 ` Andreas Schwab
2021-01-18 12:53 ` Florian Weimer via Libc-alpha
2021-01-18 18:27 ` DJ Delorie via Libc-alpha
2021-01-18 15:59 ` Carlos O'Donell via Libc-alpha
2021-01-18 16:53 ` Florian Weimer via Libc-alpha
2021-01-19 14:30 ` Carlos O'Donell via Libc-alpha
2021-01-19 14:40 ` Florian Weimer via Libc-alpha
2021-01-18 18:35 ` DJ Delorie via Libc-alpha
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2101280038500.18505@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).