From: Austin Gonyou <austin@coremetrics.com>
To: tromey@redhat.com
Cc: RH Eclipse List <eclipse@sources.redhat.com>
Subject: Re: EPIC Plugin make Eclipse crazy.
Date: Mon, 11 Aug 2003 16:05:00 -0000 [thread overview]
Message-ID: <1060617892.1951.11.camel@portageek.digitalroadkill.net> (raw)
In-Reply-To: <87brv3et6e.fsf@fleche.redhat.com>
I took a look at the .rej and it seems that whatever was in the patch
was rejected. Can you send me your .spec directly so I can see the
differences?
On Tue, 2003-08-05 at 15:38, Tom Tromey wrote:
> >>>>> "Austin" == Austin Gonyou <austin@coremetrics.com> writes:
>
> Austin> I found that I get OOM killer stepping in. As soon as I open
> Austin> *any* .pl files, it begins to die.
>
> Maybe you're running into another (unknown) bug in addition to the
> EINTR thing. It would help if you could try the EINTR patch first.
>
> Tom
--
Austin Gonyou <austin@coremetrics.com>
Coremetrics, Inc.
next prev parent reply other threads:[~2003-08-11 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 18:25 Austin Gonyou
2003-08-05 20:31 ` Austin Gonyou
2003-08-05 20:45 ` Tom Tromey
2003-08-11 16:05 ` Austin Gonyou [this message]
2003-08-12 21:41 ` Tom Tromey
2003-08-05 20:31 ` Tom Tromey
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=1060617892.1951.11.camel@portageek.digitalroadkill.net \
--to=austin@coremetrics.com \
--cc=eclipse@sources.redhat.com \
--cc=tromey@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).