From: John Darrington <john@darrington.wattle.id.au>
To: gdb-patches@sourceware.org
Subject: gdb.texinfo not building.
Date: Sat, 20 Oct 2018 11:54:00 -0000 [thread overview]
Message-ID: <20181020115417.62knz3467kw5mdqg@jocasta.intra> (raw)
This change:
commit 7806cea72329a354c36ed8b2177d03f9d5e2673f
Author: Tom Tromey <tom@tromey.com>
Date: Sun Sep 2 19:41:41 2018 -0600
Deprecate and replace the "tabset" command
Seems to have caused gdb.texinfo to no longer build.
Mismatched @table / @end table ...
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
reply other threads:[~2018-10-20 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181020115417.62knz3467kw5mdqg@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=gdb-patches@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