From: Andreas Schwab <schwab@suse.de>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix fnmatch handling of collating elements (bug 17396, bug 16976)
Date: Mon, 22 Aug 2016 07:08:00 -0000 [thread overview]
Message-ID: <mvm4m6dnuv9.fsf@hawking.suse.de> (raw)
In-Reply-To: <20160818180403.GO21655@vapier.lan> (Mike Frysinger's message of "Thu, 18 Aug 2016 11:04:03 -0700")
On Aug 18 2016, Mike Frysinger <vapier@gentoo.org> wrote:
> might be a little more readable:
> strcpy (pattern, "[[.", 3);
> memset (pattern + 3, 'a', LENGTH);
> strcpy (pattern + LENGTH + 3, ".]]", 3);
Except that it doesn't work.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-08-22 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 13:27 Andreas Schwab
2016-08-18 18:04 ` Mike Frysinger
2016-08-22 7:08 ` Andreas Schwab [this message]
2016-08-22 18:35 ` Mike Frysinger
2016-08-23 8:13 ` Andreas Schwab
2016-08-24 19:57 ` Mike Frysinger
2016-08-23 11:18 ` Pedro Alves
2017-04-05 9:35 Andreas Schwab
2018-05-24 12:36 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=mvm4m6dnuv9.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=libc-alpha@sourceware.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).