From: Mike Frysinger <vapier.adi@gmail.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, kdb@oss.sgi.com, mingo@elte.hu,
mort@sgi.com, linux-arch@vger.kernel.org
Subject: Re: [PATCH 05/37] kdb: core for kgdb back end
Date: Sat, 26 Dec 2009 16:34:02 -0500 [thread overview]
Message-ID: <8bd0f97a0912261334m4f56b8taa0b46636e62923c@mail.gmail.com> (raw)
In-Reply-To: <4B338F5B.9050904@windriver.com>
On Thu, Dec 24, 2009 at 10:57, Jason Wessel wrote:
> Peter Zijlstra wrote:
>> Please never post with kgdb-bugreport@lists.sourceforge.net
>> in the CC, it generates bounces for everything send to it.
>
> The kgdb-bugreports list has been fixed to cease the generation of
> non-subscriber notifications. All you had to do was indicate there was
> a problem. Non-subscribers are free to post there, and the messages go
> through a filter queue.
kgdb@oss.sgi.com needs fixing too it seems
-mike
next prev parent reply other threads:[~2009-12-26 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261603190-5036-1-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-2-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-3-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-4-git-send-email-jason.wessel@windriver.com>
[not found] ` <1261603190-5036-5-git-send-email-jason.wessel@windriver.com>
2009-12-23 21:19 ` [PATCH 05/37] kdb: core for kgdb back end Jason Wessel
2009-12-24 1:28 ` Andi Kleen
2009-12-28 22:36 ` Jason Wessel
2009-12-28 23:37 ` Andi Kleen
2009-12-24 11:01 ` Peter Zijlstra
2009-12-24 11:16 ` Peter Zijlstra
2009-12-24 15:57 ` Jason Wessel
2009-12-26 21:34 ` Mike Frysinger [this message]
2009-12-24 11:55 ` Jason Wessel
2009-12-24 11:55 ` Jason Wessel
2009-12-24 12:01 ` Peter Zijlstra
2009-12-24 11:04 ` Peter Zijlstra
2009-12-28 16:33 ` Jason Wessel
2009-12-28 16:55 ` Peter Zijlstra
2009-12-28 17:15 ` Jason Wessel
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=8bd0f97a0912261334m4f56b8taa0b46636e62923c@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=jason.wessel@windriver.com \
--cc=kdb@oss.sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mort@sgi.com \
--cc=peterz@infradead.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 NNTP newsgroup(s).