From: "Dave Korn" <dave.korn@artimi.com>
To: <overseers@sourceware.org>
Subject: FW: Huge memory leak, probably related to making new processes
Date: Wed, 03 Oct 2007 13:57:00 -0000 [thread overview]
Message-ID: <009401c805c5$5bb8e800$2e08a8c0@CAM.ARTIMI.COM> (raw)
On 03 October 2007 14:49, Postmaster wrote:
> The organisation to which your message was addressed now operates as part of
> the Health Protection Agency. All camr.org.uk email addresses have been
> decommissioned, therefore the intended recipient of your message will not
> have received it. Please see www.hpa.org.uk for more information.
I've received five of these bounces today. Could someone who's got a spare
minute or two perhaps unsub any camr.org.uk addresses from the cygwin list?
cheers,
DaveK
--
Can't think of a witty .sigline today....
next reply other threads:[~2007-10-03 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 13:57 Dave Korn [this message]
2007-10-03 14:52 ` Christopher Faylor
2007-10-03 14:54 ` 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='009401c805c5$5bb8e800$2e08a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=overseers@sourceware.org \
/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).