From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2627] epilogue mode probe aliases
Date: Sun, 07 May 2006 13:47:00 -0000 [thread overview]
Message-ID: <20060507134749.21714.qmail@sourceware.org> (raw)
In-Reply-To: <20060501140621.2627.fche@redhat.com>
------- Additional Comments From guanglei at cn dot ibm dot com 2006-05-07 13:47 -------
Created an attachment (id=1003)
--> (http://sourceware.org/bugzilla/attachment.cgi?id=1003&action=view)
epilogue mode alias patch
I tried to hack systemtap and worked out a patch for this bug. I don't have
much experience about the translator so forgive me if I made some silly
mistakes.
I tested this patch and it seems to work well for me.
This patch is based on CVS dated 05-07
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2627
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-05-07 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 14:06 [Bug translator/2627] New: " fche at redhat dot com
2006-05-07 13:47 ` guanglei at cn dot ibm dot com [this message]
2006-05-07 15:37 ` [Bug translator/2627] " fche at redhat dot com
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=20060507134749.21714.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).