From: William Cohen <wcohen@redhat.com>
To: Jim Keniston <jkenisto@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: Write-up on submitting systemtap examples
Date: Mon, 11 May 2009 21:43:00 -0000 [thread overview]
Message-ID: <4A089BEA.7060502@redhat.com> (raw)
In-Reply-To: <1242058894.3432.12.camel@dyn9047018094.beaverton.ibm.com>
Jim Keniston wrote:
> On Mon, 2009-05-11 at 10:43 -0400, William Cohen wrote:
>> Hi All,
>>
>> Trying to streamline the process of people submitting systemtap examples. Below
>> is a writeup trying to cover what to do for submitting examples. Comments on it
>> would be appreciated. Expect that this text would go in the
>> testsuite/systemtap.examples directory and be like the HACKING file in the root
>> of systemtap source code.
>>
>> -Will
>
> Looks good. See below for suggested tweaks. Thanks for your work on
> this.
>
> Jim
Hi Jim,
Thanks for the comments on the writeup. I merge the writeup into the
testsuite/systemtap.examples/README.
-Will
prev parent reply other threads:[~2009-05-11 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:44 William Cohen
2009-05-11 16:21 ` Jim Keniston
2009-05-11 21:43 ` William Cohen [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=4A089BEA.7060502@redhat.com \
--to=wcohen@redhat.com \
--cc=jkenisto@us.ibm.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).