From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: What made this bug report better?
Date: Tue, 24 Feb 2009 08:16:12 +0000 [thread overview]
Message-ID: <20090224081612.GA6160@silver.sucs.org> (raw)
In-Reply-To: <200902241343.22762.rusty@rustcorp.com.au>
On Tue, Feb 24, 2009 at 01:43:22PM +1030, Rusty Russell wrote:
> On Friday 20 February 2009 20:57:05 Sitsofe Wheeler wrote:
> > What happened this time that made things succesful? Was the original
> > mail too big? Did it not make it to the list?
>
> Frederic was the difference; he pulled me in by CC'ing me, once he figured
> out it was my bug.
Rusty, Ingo: Thanks for letting me know!
Frederic: What information are you looking for in bug reports? What sort
of areas interest you?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-02-24 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 16:09 Poking ieee80211_default_rc_algo causes kernel lockups Sitsofe Wheeler
2009-02-15 17:02 ` Frederic Weisbecker
2009-02-15 19:24 ` Sitsofe Wheeler
2009-02-15 19:41 ` Frederic Weisbecker
2009-02-15 21:02 ` Sitsofe Wheeler
2009-02-16 1:40 ` Frederic Weisbecker
2009-02-16 2:37 ` Frederic Weisbecker
2009-02-15 19:35 ` Frederic Weisbecker
2009-02-16 10:10 ` Rusty Russell
2009-02-16 17:59 ` Frederic Weisbecker
2009-02-16 23:37 ` Rusty Russell
2009-02-20 10:27 ` What made this bug report better? (was Re: Poking ieee80211_default_rc_algo causes kernel lockups) Sitsofe Wheeler
2009-02-20 11:31 ` Ingo Molnar
2009-02-24 3:13 ` Rusty Russell
2009-02-24 8:16 ` Sitsofe Wheeler [this message]
2009-02-24 17:58 ` What made this bug report better? Frederic Weisbecker
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=20090224081612.GA6160@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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.