From: Rob Savoye <rob@welcomehome.org>
To: Jason Merrill <jason_merrill@redhat.com>
Cc: gdb-patches@sources.redhat.com, sid@sources.redhat.com
Subject: Re: Small PATCH to dejagnu/lib/utils.exp
Date: Tue, 17 Jul 2001 09:11:00 -0000 [thread overview]
Message-ID: <20010717102343.G6783@welcomehome.org> (raw)
In-Reply-To: <m3k817wq4c.fsf@prospero.cambridge.redhat.com>
On Tue, Jul 17, 2001 at 04:07:47PM +0100, Jason Merrill wrote:
> This patch tweaks runtest_file_p so that a user can say
> "foo.exp=bar/baz.C"; currently only "foo.exp=baz.C" and
> "foo.exp=/full/path/to/bar/baz.C" are accepted. I suppose the user could
> provide the initial wildcard themselves, but this seems more friendly.
>
> The patch also corrects the erroneous documentation for the function.
>
> OK to apply? Anyone?
>
> 2001-07-17 Jason Merrill <jason_merrill@redhat.com>
>
> * lib/utils.exp (runtest_file_p): An argument can match trailing
> directories as well as the basename.
>
This patch looks ok to me.
- rob -
prev parent reply other threads:[~2001-07-17 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 8:09 Jason Merrill
2001-07-17 9:11 ` Rob Savoye [this message]
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=20010717102343.G6783@welcomehome.org \
--to=rob@welcomehome.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jason_merrill@redhat.com \
--cc=sid@sources.redhat.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).