From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, binutils@sources.redhat.com,
gcc@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: expect 5.39 import
Date: Thu, 21 Aug 2003 21:34:00 -0000 [thread overview]
Message-ID: <200308212134.h7LLYVWr032104@duracef.shout.net> (raw)
Wow, I didn't even know the new expect release. I gotta give
that a spin.
I've been using expect 5.38 in my test bed and it's been working fine.
Back in January 2003, I compared expect 5.38 with sourceware expect,
and the gdb test results were the same.
> I'll follow this up in a few weeks when I'm actually in a position to do
> an import.
Can you file a PR and then I'll attach my attestation to it?
By the time "a few weeks" comes up I'll have something to say about
expect 5.39 too.
Michael C
next reply other threads:[~2003-08-21 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 21:34 Michael Elizabeth Chastain [this message]
2003-08-21 22:28 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 20:52 Andrew Cagney
[not found] ` <m34r0ayxxa.fsf@redhat.com>
2003-08-22 14:56 ` 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=200308212134.h7LLYVWr032104@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@sources.redhat.com \
--cc=gdb@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