From: "Phil Betts" <Phil.Betts@ascribe.com>
To: <cygwin-talk@cygwin.com>
Subject: RE: [1.7] Weird error "grep: writing output: Cannot allocate memory"
Date: Tue, 05 May 2009 12:26:00 -0000 [thread overview]
Message-ID: <5E25AF06EFB9EA4A87C19BC98F5C875303339151@core-email.int.ascribe.com> (raw)
In-Reply-To: <49FF4BE6.5020208@gmail.com>
Dave Korn wrote:
> If only those fools upstream would open their source, we could have
> fixed
> the underlying bug for them... ;-)
That's crazy talk Dave! Their entire business model is based on
people "upgrading" in the hope that longstanding, obvious bugs will be
fixed (Word *still* has bugs I first reported to them about 18 years
ago). If the bugs were fixed, the whole house of cards would collapse.
Phil
--
This email has been scanned by Ascribe Ltd using Microsoft Antigen for Exchange.
next parent reply other threads:[~2009-05-05 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49FB714A.4010002@gmail.com>
[not found] ` <20090504033921.GA6162@ednor.casa.cgf.cx>
[not found] ` <20090504035236.GA11270@ednor.casa.cgf.cx>
[not found] ` <49FF4BE6.5020208@gmail.com>
2009-05-05 12:26 ` Phil Betts [this message]
2009-05-05 12:41 ` Dave Korn
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=5E25AF06EFB9EA4A87C19BC98F5C875303339151@core-email.int.ascribe.com \
--to=phil.betts@ascribe.com \
--cc=cygwin-talk@cygwin.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).