From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dustin Lang <dalang@cs.ubc.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
"Redondo Garcia, Roberto" <rredondo@indra.es>
Subject: Re: back trace when a SIGSEGV
Date: Mon, 05 Dec 2005 12:23:56 +1100 [thread overview]
Message-ID: <1133745837.6100.121.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.60.0512041654330.16831@tin.icics.ubc.ca>
On Sun, 2005-12-04 at 17:20 -0800, Dustin Lang wrote:
> Hi,
>
> > You don't need to play the cop on this list, nobody appointed you to
> > that position.
>
> Fair enough. But do you think my reply, over all, was unreasonable?[1] I
> made an attempt to answer his question, pointing out two of the most
> useful resources. I also told him that his question wasn't really suited
> to the list - I would have listed some better resources but I'm not
> familiar with any - but I tried to write a balanced,
> gentle-push-in-the-right-direction, sort of message. Re-reading the
> snippet you highlighted, it does sound rude. It wasn't meant to be.
> (Roberto, please accept my apologies!)
The s/n ratio of this list is good enough to make such occasional
questions acceptable.
Ben.
next prev parent reply other threads:[~2005-12-05 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 10:33 back trace when a SIGSEGV Redondo Garcia, Roberto
2005-12-02 14:27 ` Dustin Lang
2005-12-04 22:14 ` Benjamin Herrenschmidt
2005-12-05 1:20 ` Dustin Lang
2005-12-05 1:23 ` Benjamin Herrenschmidt [this message]
2005-12-02 15:35 ` Wolfgang Denk
2005-12-04 22:16 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 10:29 Redondo Garcia, Roberto
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=1133745837.6100.121.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=dalang@cs.ubc.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=rredondo@indra.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.