From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)]
Date: Mon, 10 Oct 2011 16:15:00 -0000 [thread overview]
Message-ID: <20111010161434.GA13866@host1.jankratochvil.net> (raw)
In-Reply-To: <83sjn0ygir.fsf@gnu.org>
On Mon, 10 Oct 2011 18:10:04 +0200, Eli Zaretskii wrote:
> That'd be fine, but there's no good way in Texinfo to test for the
> version of makeinfo. So what exactly would be the condition for using
> the alternative?
There is already the feature test in my last patch by autoconf. Going to post
the alternative (ASCII art?) variant in a moment.
Thanks,
Jan
next prev parent reply other threads:[~2011-10-10 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 19:50 [patch 04/12] entryval#3: Virtual tail call frames Jan Kratochvil
2011-10-09 19:27 ` [commit] " Jan Kratochvil
2011-10-09 20:23 ` Jan Kratochvil
2011-10-10 13:40 ` doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames) Ulrich Weigand
2011-10-10 13:54 ` Eli Zaretskii
2011-10-10 13:58 ` Ulrich Weigand
2011-10-10 14:58 ` [patch] New test+use texinfo @click - @HAVE_MAKEINFO_CLICK@ [Re: doc build failure (Re: [patch 04/12] entryval#3: Virtual tail call frames)] Jan Kratochvil
2011-10-10 15:16 ` Pedro Alves
2011-10-10 15:31 ` Jan Kratochvil
2011-10-10 15:51 ` Pedro Alves
2011-10-10 18:47 ` Jan Kratochvil
2011-10-10 19:11 ` Eli Zaretskii
2011-10-10 21:56 ` Pedro Alves
2011-10-10 22:19 ` Andreas Schwab
2011-10-11 23:34 ` Jan Kratochvil
2011-10-12 15:26 ` Pedro Alves
2011-10-12 15:56 ` Jan Kratochvil
2011-10-25 14:35 ` Joel Brobecker
2011-10-25 14:47 ` Jan Kratochvil
2011-10-25 16:09 ` Joel Brobecker
2011-10-10 16:10 ` Eli Zaretskii
2011-10-10 16:15 ` Jan Kratochvil [this message]
2011-10-10 16:09 ` Eli Zaretskii
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=20111010161434.GA13866@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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