From: Eli Zaretskii <eliz@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: simark@simark.ca, tom@tromey.com, gdb-patches@sourceware.org,
brobecker@adacore.com, fejfighter@gmail.com
Subject: Re: [PATCH] Add epub output for documentation
Date: Wed, 09 Nov 2022 19:09:26 +0200 [thread overview]
Message-ID: <83cz9wt5q1.fsf@gnu.org> (raw)
In-Reply-To: <Y2vbDLTBgRex4cHi@vapier> (message from Mike Frysinger on Wed, 9 Nov 2022 23:53:32 +0700)
> Date: Wed, 9 Nov 2022 23:53:32 +0700
> From: Mike Frysinger <vapier@gentoo.org>
> Cc: Tom Tromey <tom@tromey.com>,
> Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>,
> Eli Zaretskii <eliz@gnu.org>,
> Joel Brobecker <brobecker@adacore.com>, fejfighter@gmail.com
>
> that said, having an "install-epub" rule in gdb alone (and in the doc/
> subdir at that) seems pretty questionable. seems like someone who is
> interested in moving the epub needle should spend the time pushing it
> through all the GNU parts, assuming the texinfo people aren't already.
>
> there's certainly autoconf as you highlight, but also the GNU standards,
> and the GCC top-level, and binutils/gdb top-level, and automake, and the
> binutils/gdb release scripts so things get published to the websites.
> that's off the top of my head, but i'm sure there's more.
Right, I wrote to the Texinfo list about that.
next prev parent reply other threads:[~2022-11-09 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 7:54 Fejfighter
2022-11-09 12:38 ` Eli Zaretskii
2022-11-09 13:21 ` Simon Marchi
2022-11-09 13:22 ` Eli Zaretskii
2022-11-09 13:41 ` Simon Marchi
2022-11-09 13:44 ` Eli Zaretskii
2022-11-09 13:48 ` Simon Marchi
2022-11-09 15:48 ` Tom Tromey
2022-11-09 16:15 ` Simon Marchi
2022-11-09 16:53 ` Mike Frysinger
2022-11-09 17:09 ` Eli Zaretskii [this message]
2022-11-09 16:48 ` 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=83cz9wt5q1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=fejfighter@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).