From: Pedro Alves <palves@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>,
Doug Evans <xdje42@gmail.com>, Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Documentation build regressions
Date: Thu, 31 May 2018 17:51:00 -0000 [thread overview]
Message-ID: <5dfbff95-6590-35b1-4732-c2fa104804cf@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk>
This suggests to me that we should make the buildbot
build the documentation in its various formats.
Is that done already? Maybe I missed it.
From a quick look at the Makefiles, maybe something around:
make -C gdb diststuff; make -C gdb/doc all-doc pdf html
Thanks,
Pedro Alves
prev parent reply other threads:[~2018-05-31 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 17:59 Maciej W. Rozycki
2018-05-30 20:12 ` Tom Tromey
2018-05-30 20:56 ` Jan Kratochvil
2018-05-31 17:23 ` Joseph Myers
2018-06-01 14:01 ` Jan Kratochvil
2018-06-01 19:38 ` Joseph Myers
2018-06-04 20:27 ` Maciej W. Rozycki
2018-06-05 9:49 ` variable displayed twice when using GDB/MI Xavier Roirand
2018-06-07 11:33 ` Pedro Alves
2018-05-31 17:51 ` Pedro Alves [this message]
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=5dfbff95-6590-35b1-4732-c2fa104804cf@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=macro@mips.com \
--cc=pmuldoon@redhat.com \
--cc=xdje42@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