public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simark@simark.ca>,
	 fejfighter@gmail.com
Subject: Re: [PATCH] Add epub output for documentation
Date: Wed, 09 Nov 2022 08:48:41 -0700	[thread overview]
Message-ID: <87leok2ko6.fsf@tromey.com> (raw)
In-Reply-To: <e9661ee7-d084-7076-294f-7f426472485e@simark.ca> (Simon Marchi via Gdb-patches's message of "Wed, 9 Nov 2022 08:48:58 -0500")

>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:

Simon> "make install" only installs the man pages and the info version of the
Simon> manual.  The pdf or html versions of the manual are only installed with
Simon> explicit "install-pdf" and "install-html" rules.  So I presume that epub
Simon> would be the same as pdf and html.

I think so too.  Is there a typical GNU directory for where exactly
these should be installed?

Tom

  reply	other threads:[~2022-11-09 15:49 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 [this message]
2022-11-09 16:15               ` Simon Marchi
2022-11-09 16:53                 ` Mike Frysinger
2022-11-09 17:09                   ` Eli Zaretskii
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=87leok2ko6.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=fejfighter@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).