From: Stan Shebs <stanshebs@earthlink.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: barry.wealand@lmco.com, gdb@sourceware.org
Subject: Re: Reconciling PowerPC simulator traces with performance monitor results
Date: Tue, 20 Mar 2007 19:55:00 -0000 [thread overview]
Message-ID: <46003BD6.2050503@earthlink.net> (raw)
In-Reply-To: <200703201934.l2KJYPU2025946@brahms.sibelius.xs4all.nl>
Mark Kettenis wrote:
> Sorry, Barry, but I can't help you here since Lockheed Martin still
> makes cluster bombs. And I hope other people on this list won't help
> you either.
>
I appreciate the sentiment, but let's not go there - this is all
complicated enough without having to evaluate the politics of every
request. If you work at it, you can find a reason to attack anybody for
things for which they are not personally responsible.
Stan
next prev parent reply other threads:[~2007-03-20 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 17:52 Wealand, Barry
2007-03-20 19:34 ` Mark Kettenis
2007-03-20 19:49 ` Paul Koning
2007-03-20 19:55 ` Stan Shebs [this message]
2007-03-20 18:35 Wealand, Barry
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=46003BD6.2050503@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=barry.wealand@lmco.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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