From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: "zap splat blong" <cygwin-talk@cygwin.com>
Subject: RE: 1.5.19-4 & snapshot-20060529 : crash when freeing null std::string in dll (resend for attachment renaming)
Date: Wed, 07 Jun 2006 16:20:00 -0000 [thread overview]
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F548F82@PAUMAILU03.ags.agere.com> (raw)
Dave Korn (no, not THAT one!) wrote:
> At least I didn't reply to his post and inadvertently quote
> the entire tarball in uucode/b64 though. I've seen that happen!
In the body or the subject line?
gsw
next reply other threads:[~2006-06-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:20 Williams, Gerald S (Jerry) [this message]
2006-06-07 16:25 ` Dave Korn
[not found] <447DE070.6070609@gmail.com>
[not found] ` <03e901c684e0$fbf906e0$a501a8c0@CAM.ARTIMI.COM>
2006-05-31 19:44 ` mwoehlke
2006-06-01 9:29 ` 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=4C89134832705D4D85A6CD2EBF38AE0F548F82@PAUMAILU03.ags.agere.com \
--to=gsw@agere.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).