From: Jim Meyering <jim@meyering.net>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>
Subject: Re: Your gnulib patch
Date: Wed, 1 Jan 2020 19:41:42 -0800 [thread overview]
Message-ID: <CA+8g5KEGM0uOZy9W=oUrP=RsquF-LqxnvxZjbXgQTc+mkRPKFA@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpVNAgNU-yvyhKrtNJqxqDfXwvNBt1ty4+gmARtDyjNXrA@mail.gmail.com>
On Tue, Dec 24, 2019 at 11:13 AM Cong Wang <xiyou.wangcong@gmail.com> wrote:
> Hello, Jim
>
> We found your gnulib patch
> (http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=47cb657e)
> quite useful for us, as we encountered a same issue with a few million
> files under one directory.
>
> Is it possible for you to integrate the patch to glibc too? Our
> project doesn't use gnulib at all, so it would benefit more people if
> you could integrate it to glibc. :) I understand that would bring you
> more work, if I have your permission, I can help on that too. Please
> let me know how you would like to proceed.
Hi Cong Wang,
Thanks for your interest and the offer to contribute.
If you'd like that functionality in glibc, note that it would have to
use different function names, because the gnulib version of fts uses a
different API (e.g., numerous struct changes were required to remove
limitations in the glibc version).
You are welcome to pursue adding it to glibc, of course.
next parent reply other threads:[~2020-01-02 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM_iQpVNAgNU-yvyhKrtNJqxqDfXwvNBt1ty4+gmARtDyjNXrA@mail.gmail.com>
2020-01-02 3:41 ` Jim Meyering [this message]
2020-01-03 22:43 ` Your gnulib patch Cong Wang
2020-01-03 23:30 ` Jim Meyering
2020-01-08 0:41 ` Cong Wang
2020-01-08 1:43 ` 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='CA+8g5KEGM0uOZy9W=oUrP=RsquF-LqxnvxZjbXgQTc+mkRPKFA@mail.gmail.com' \
--to=jim@meyering.net \
--cc=bug-gnulib@gnu.org \
--cc=xiyou.wangcong@gmail.com \
/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).