unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: glob vs '*/' vs GLOB_ONLYDIR vs xfs
Date: Fri, 06 Aug 2021 18:03:31 -0400	[thread overview]
Message-ID: <xnpmuqnscs.fsf@greed.delorie.com> (raw)
In-Reply-To: <aa3f7b11-7aaf-d986-f92c-516811c10cf7@cs.ucla.edu>

Paul Eggert <eggert@cs.ucla.edu> writes:
> I plan to address this by merging recent glibc glob changes into
> Gnulib (these were for 64-bit time_t), fixing the bug in Gnulib, and
> then we can talk about merging back.
>
> The fix won't be trivial, unfortunately. On the bright side, I think we 
> can remove some more stat/lstat calls from glob.

Excellent.  Thanks!


      reply	other threads:[~2021-08-06 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  3:24 glob vs '*/' vs GLOB_ONLYDIR vs xfs DJ Delorie via Libc-alpha
2021-08-05  8:10 ` Paul Eggert
2021-08-05 18:10   ` DJ Delorie via Libc-alpha
2021-08-06 21:47     ` Paul Eggert
2021-08-06 22:03       ` DJ Delorie via Libc-alpha [this message]

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=xnpmuqnscs.fsf@greed.delorie.com \
    --to=libc-alpha@sourceware.org \
    --cc=dj@redhat.com \
    --cc=eggert@cs.ucla.edu \
    /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).