From: Bruno Haible <bruno@clisp.org>
To: Simon Josefsson <simon@josefsson.org>
Cc: bug-gnulib@gnu.org, Jim Meyering <jim@meyering.net>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: fts: Document this module
Date: Fri, 20 Jan 2023 00:41:47 +0100 [thread overview]
Message-ID: <8008067.n2SeQjunJ6@nimes> (raw)
In-Reply-To: <87r0vqhzku.fsf@josefsson.org>
> The gnulib fts is different from glibc API, and they can return
> different results when called the same way. See end of earlier thread
> here:
>
> https://lists.gnu.org/archive/html/bug-gnulib/2021-07/msg00070.html
Thanks for the heads-up, Simon.
> I'm not sure what could be done. Perhaps adding a sentence to the
> gnulib documentation stating that the gnulib fts is not a drop-in
> replacement for missing fts functionality but a separate implementation
> with different behaviour.
I'm not sure about what to write either. Jim or Paul, what should we state
— either in the 'fts' module description, or in the .texi documentation?
Bruno
next prev parent reply other threads:[~2023-01-19 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:38 fts: Document this module Bruno Haible
2023-01-19 23:30 ` Simon Josefsson via Gnulib discussion list
2023-01-19 23:41 ` Bruno Haible [this message]
2023-01-20 3:05 ` Paul Eggert
2023-01-20 5:24 ` Jim Meyering
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=8008067.n2SeQjunJ6@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jim@meyering.net \
--cc=simon@josefsson.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).