From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/11077] URLs in the HTML documentation are not meaningful
Date: Thu, 17 Dec 2009 20:20:00 -0000 [thread overview]
Message-ID: <20091217201957.1099.qmail@sourceware.org> (raw)
In-Reply-To: <20091210160213.11077.dmalcolm@redhat.com>
------- Additional Comments From wcohen at redhat dot com 2009-12-17 20:19 -------
Revise the generation of the documentation so that the files names are based on
the chapter names. However, the indices into the interior of the html files are
still rather cryptic labelling. latex2html doesn't seem to have a way to
generate some more human friendly labels for the index.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11077
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-12-17 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-12-17 20:30 ` dmalcolm at redhat dot com
[not found] <bug-11077-6586@http.sourceware.org/bugzilla/>
2013-07-12 22:23 ` 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=20091217201957.1099.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).