From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: fnmatch: rely on more gnulib modules
Date: Sat, 30 May 2020 01:27:30 +0200 [thread overview]
Message-ID: <2477581.nMP97CdPCx@omega> (raw)
In-Reply-To: <3149f7dc-fd9d-edd3-5fc2-b2347ad1ee5f@cs.ucla.edu>
> > Paul, is this OK from the perspective of a future merge with glibc?
>
> Yes, it's an improvement in that department; thanks.
OK. I've pushed it.
Bruno
next prev parent reply other threads:[~2020-05-29 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 12:02 fnmatch: rely on more gnulib modules Bruno Haible
2020-05-29 20:54 ` Paul Eggert
2020-05-29 23:27 ` Bruno Haible [this message]
2020-05-30 23:53 ` Paul Eggert
2020-05-31 0:14 ` Bruno Haible
2020-05-31 0:51 ` Bruno Haible
2020-05-31 17:19 ` Paul Eggert
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=2477581.nMP97CdPCx@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--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).