From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: fnmatch and invalid multibyte characters
Date: Thu, 28 Nov 2002 10:31:00 -0000 [thread overview]
Message-ID: <3DE660FC.6030403@redhat.com> (raw)
In-Reply-To: <jevg2h4wl5.fsf@sykes.suse.de>
Andreas Schwab wrote:
> When fnmatch detects an invalid multibyte character it should fall back to
> single byte matching, so that "*" has a chance to match such a string.
And why is this better or more correct? Is there existing practice?
--
--------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
next prev parent reply other threads:[~2002-11-28 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 6:07 Andreas Schwab
2002-11-28 10:31 ` Ulrich Drepper [this message]
2002-11-29 1:58 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DE660FC.6030403@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwab@suse.de \
/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).