From: Yao Qi <yao@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mingjie Xing <mingjie.xing@gmail.com>, <gdb@sourceware.org>
Subject: Re: Gdb online docs error?
Date: Tue, 22 May 2012 04:39:00 -0000 [thread overview]
Message-ID: <4FBB1884.5090203@codesourcery.com> (raw)
In-Reply-To: <20120518165500.GQ29339@adacore.com>
On 05/19/2012 12:55 AM, Joel Brobecker wrote:
>> > I don't know how these html files are synced to sourceware.org server,
>> > but I guess there might be some problem there.
> Maybe the tools on sourceware are too old for the current documentation,
> I am not sure. I can take a look, but just don't have the time for
> another 10-15 days :-(. Can we see if the documentation from the
> last release was properly generated?
I get a build on gdb-7.4.1 release on my box. Both missing files, as
reported, Command-Files.html and GDB_002fMI-Command-Syntax.html are
generated properly. However, the pdf version got from
http://sourceware.org/gdb/current/onlinedocs/gdb.pdf.gz looks correct.
A lot users reference gdb html doc on sourceware.org, so it is not good
to give them a "page not found" error. I am happy to help on this, but
don't know what I can do.
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-05-22 4:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 5:27 Mingjie Xing
2012-05-18 14:13 ` Yao Qi
2012-05-18 16:55 ` Joel Brobecker
2012-05-22 4:39 ` Yao Qi [this message]
2012-05-25 22:00 ` Sergio Durigan Junior
2012-05-18 17:47 ` Matt Rice
2012-05-27 14:57 ` Joel Brobecker
2012-05-28 14:08 ` Joel Brobecker
2012-05-29 18:53 ` Sergio Durigan Junior
2012-06-07 16:52 ` Joel Brobecker
2012-06-07 17:58 ` mikhail.terekhov
2012-06-07 21:54 ` Joel Brobecker
2012-06-07 22:10 ` Joel Brobecker
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=4FBB1884.5090203@codesourcery.com \
--to=yao@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mingjie.xing@gmail.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).