From: Eugene Teo <eteo@redhat.com>
To: Kevin Feliksa <feliksa@us.ibm.com>
Cc: systemtap@sourceware.org
Subject: Re: Hi - I'm writing SystemTap installation documentation
Date: Wed, 07 Jun 2006 00:41:00 -0000 [thread overview]
Message-ID: <448620B0.40803@redhat.com> (raw)
In-Reply-To: <OF3A8797F0.63D7A1F8-ON87257185.0078161A-05257185.0077B06C@us.ibm.com>
Kevin Feliksa wrote:
> My name is Kevin Feliksa and I'm preparing SystemTap installation
> documentation - currently for Fedora core 5, and later for several other
> distros. Since it can be said with much certainty that many developers
> cringe at even the thought of creating these (essential) documents, let me
> be your ally in helping to make SystemTap the best!
The documentation for FC5 is pretty straight-forward, and it's already
available at http://sourceware.org/systemtap/build.html
Eugene
prev parent reply other threads:[~2006-06-07 0:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 21:47 Kevin Feliksa
2006-06-07 0:41 ` Eugene Teo [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=448620B0.40803@redhat.com \
--to=eteo@redhat.com \
--cc=feliksa@us.ibm.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).