From: Jim Ingham <jingham@apple.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Joern Rennecke <joern.rennecke@superh.com>,
Aldy Hernandez <aldyh@redhat.com>,
Andreas Tobler <toa@pop.agri.ch>, GCC <gcc@gcc.gnu.org>
Subject: Re: Subject: Kernel bugs that trip expect (Was: Re: 2 new regression on darwin6.1)
Date: Tue, 15 Oct 2002 13:02:00 -0000 [thread overview]
Message-ID: <2B9F8795-E06F-11D6-BBA1-00039379E320@apple.com> (raw)
In-Reply-To: <20021015093441.A17165@lucon.org>
Great, thanks... This also needs to be submitted to
sources.redhat.com, since they maintain a separate version of expect,
and I don't know how often they resync with the net version...
Jim
On Tuesday, October 15, 2002, at 09:34 AM, H. J. Lu wrote:
> On Mon, Oct 14, 2002 at 10:33:23AM -0700, Jim Ingham wrote:
>> If you have expect patches have you submitted them back to the expect
>> maintainers? This is now hosted at SourceForge.
>>
>> This won't help gcc & gdb, because they use a weird hacked version of
>> expect - the current expect won't run the testsuite correctly. But if
>> you have found some Linux bug, you should submit a patch to the
>> SourceForge patch tracker...
>>
>
> https://sourceforge.net/tracker/
> index.php?func=detail&aid=623629&group_id=13179&atid=313179
>
>
>
> H.J.
>
--
Jim Ingham jingham@apple.com
Developer Tools
Apple Computer
next prev parent reply other threads:[~2002-10-15 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 10:34 Joern Rennecke
2002-10-14 10:58 ` H. J. Lu
2002-10-14 11:00 ` Jim Ingham
2002-10-14 11:38 ` Joern Rennecke
2002-10-14 12:31 ` H. J. Lu
2002-10-15 7:24 ` Joern Rennecke
2002-10-15 7:28 ` H. J. Lu
2002-10-15 10:58 ` H. J. Lu
2002-10-15 13:02 ` Jim Ingham [this message]
2002-10-15 13:19 ` H. J. Lu
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=2B9F8795-E06F-11D6-BBA1-00039379E320@apple.com \
--to=jingham@apple.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=joern.rennecke@superh.com \
--cc=toa@pop.agri.ch \
/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).