From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: try_catch.cc -> try-catch.cc
Date: Wed, 29 May 2002 22:00:00 -0000 [thread overview]
Message-ID: <200205300456.g4U4uS215951@duracef.shout.net> (raw)
Andrew Cagney writes:
> Anyway, your call. (Hmm, we desperatly need some file name completer
> tests including some containing spaces.)
Thanks.
I'm going to go with try_catch.c, as is.
Michael C
next reply other threads:[~2002-05-30 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 22:00 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 12:01 Michael Elizabeth Chastain
2002-05-29 20:46 ` Andrew Cagney
2002-05-30 1:42 ` Daniel Jacobowitz
2002-05-29 10:08 Andrew Cagney
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=200205300456.g4U4uS215951@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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