From: "smakarov at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/14146] New: tapset::* man pages should be generated from actual tapset files
Date: Wed, 23 May 2012 15:18:00 -0000 [thread overview]
Message-ID: <bug-14146-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14146
Bug #: 14146
Summary: tapset::* man pages should be generated from actual
tapset files
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: documentation
AssignedTo: systemtap@sourceware.org
ReportedBy: smakarov@redhat.com
Classification: Unclassified
Currently, the man/tapset::*.3stap manual pages are hand-written. This is
unnecessary and error-prone duplication, as they could just as easily be
auto-generated from the comments in the corresponding .stp file (as is already
done for the tapset reference manual).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-05-23 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 15:18 smakarov at redhat dot com [this message]
2012-05-24 18:58 ` [Bug documentation/14146] " smakarov 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=bug-14146-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).