From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/11210] 3stap man pages colliding with 3
Date: Fri, 05 Feb 2010 16:48:00 -0000 [thread overview]
Message-ID: <20100205164835.14143.qmail@sourceware.org> (raw)
In-Reply-To: <20100122010129.11210.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2010-02-05 16:48 -------
That looks great in theory. Have you tried it just via
manual renaming? If so, then it is only a matter of
changing the names at 'make install' time or earlier.
Do we need to retain the "3stap" suffix in this case?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11210
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2010-02-05 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 1:01 [Bug documentation/11210] New: " fche at redhat dot com
2010-02-05 16:39 ` [Bug documentation/11210] " dsmith at redhat dot com
2010-02-05 16:48 ` fche at redhat dot com [this message]
2010-02-05 18:04 ` dsmith at redhat dot com
2010-03-08 18:55 ` wcohen 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=20100205164835.14143.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).