public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: libc-hacker@sourceware.org
Subject: Re: [PATCH] Fix glob with empty pattern and patterns ending in slash
Date: Wed, 24 Mar 2010 19:01:00 -0000	[thread overview]
Message-ID: <4BAA6184.2090503@redhat.com> (raw)
In-Reply-To: <m3zl20bd8o.fsf@hase.home>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I see the problem with empty patterns and check in a slightly changed
patch for that.  What is the issue with trailing slashes?  I need a test
case.  For the other change there also should have been a test case.

- -- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkuqYYQACgkQ2ijCOnn/RHT3uwCeOczWg6VpNUuL7mg1LprYP0DU
ZoYAn2t8oVH/EoajN6IQZsiIrmXEqk34
=0+ar
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-03-24 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 15:14 Andreas Schwab
2010-03-24 19:01 ` Ulrich Drepper [this message]
2010-03-25 10:07   ` 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=4BAA6184.2090503@redhat.com \
    --to=drepper@redhat.com \
    --cc=libc-hacker@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).