From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/11077] URLs in the HTML documentation are not meaningful
Date: Fri, 12 Jul 2013 22:23:00 -0000 [thread overview]
Message-ID: <bug-11077-6586-5bLDYXNigf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11077-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11077
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |WONTFIX
--- Comment #4 from Frank Ch. Eigler <fche at redhat dot com> ---
too small an issue to solve
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2013-07-12 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11077-6586@http.sourceware.org/bugzilla/>
2013-07-12 22:23 ` fche at redhat dot com [this message]
2009-12-10 16:02 [Bug documentation/11077] New: " dmalcolm at redhat dot com
2009-12-15 21:45 ` [Bug documentation/11077] " wcohen at redhat dot com
2009-12-17 20:20 ` wcohen at redhat dot com
2009-12-17 20:30 ` dmalcolm 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-11077-6586-5bLDYXNigf@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).