From: "Frank Ch. Eigler" <fche@redhat.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap@sources.redhat.com
Subject: Re: notification for systemtap-related oops
Date: Fri, 16 May 2008 16:23:16 -0400 [thread overview]
Message-ID: <20080516202316.GD714@redhat.com> (raw)
In-Reply-To: <482DE4D1.5020608@linux.intel.com>
Hi -
On Fri, May 16, 2008 at 12:47:29PM -0700, Arjan van de Ven wrote:
> I can get you an RSS feed for [notifying us of stap* oopses]....
> doing something more proactive is harder due to the unscalable nature
RSS would be fine, and can be converted to email by other tools.
- FChE
prev parent reply other threads:[~2008-05-16 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 16:41 Top kernel oopses/warnings for the week of May 16th 2008 Arjan van de Ven
2008-05-16 17:14 ` Evgeniy Polyakov
2008-05-16 18:04 ` Adrian Bunk
2008-05-16 18:19 ` Arjan van de Ven
2008-05-20 3:53 ` Dave Jones
2008-05-16 18:50 ` notification for systemtap-related oops Frank Ch. Eigler
2008-05-16 19:47 ` Arjan van de Ven
2008-05-16 20:23 ` Frank Ch. Eigler [this message]
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=20080516202316.GD714@redhat.com \
--to=fche@redhat.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sources.redhat.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