From: Tom Tromey <tom@tromey.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: <gdb@sourceware.org>
Subject: Re: Documentation build regressions
Date: Wed, 30 May 2018 20:12:00 -0000 [thread overview]
Message-ID: <87a7sgdhsd.fsf@tromey.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1805301840590.10896@tp.orcam.me.uk> (Maciej W. Rozycki's message of "Wed, 30 May 2018 18:59:01 +0100")
>>>>> "Maciej" == Maciej W Rozycki <macro@mips.com> writes:
Maciej> You surely must have verified your changes before committing and the
Maciej> former one is especially old, so am I missing something? I find it hard
Maciej> to believe nobody has tripped over it so far.
FWIW I normally test doc changes with "make info" but basically never
with "make pdf".
Tom
next prev parent reply other threads:[~2018-05-30 20:12 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 [this message]
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 ` Documentation build regressions Pedro Alves
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=87a7sgdhsd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=macro@mips.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