From: Roland McGrath <roland@redhat.com>
To: systemtap@sources.redhat.com
Subject: utrace-devel@redhat.com mailing list
Date: Thu, 26 Jul 2007 10:19:00 -0000 [thread overview]
Message-ID: <20070726091559.0E2B94D05A9@magilla.localdomain> (raw)
A few people not involved with this project or the other one asked for a
mailing list devoted to utrace development, so I've created one. This list
will now be the main place to discuss bugs in utrace, questions about using
the utrace in-kernel APIs, porting utrace, integrating utrace, and writing
general-purpose reusable utrace-based components that can be employed by
more than one particular tracing engine. The list will be open to all
subscribers, archives are public, and posting is not restricted to members
(unless noise becomes a problem, then it may be).
Subscription details at: https://www.redhat.com/mailman/listinfo/utrace-devel
Please avoid cross-posting. You can always refer people on another project
list to a utrace-devel thread they might like to join, or vice versa.
Thanks,
Roland
reply other threads:[~2007-07-26 9:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070726091559.0E2B94D05A9@magilla.localdomain \
--to=roland@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).