From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: install-html and install-pdf improvements
Date: Fri, 17 Apr 2009 15:26:00 -0000 [thread overview]
Message-ID: <83hc0njo9e.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0904171142490.1168@digraph.polyomino.org.uk>
> Date: Fri, 17 Apr 2009 11:47:39 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
>
> This patch improves "make install-html" and "make install-pdf" support
> for GDB:
>
> * There are toplevel configure options --with-htmldir and
> --with-pdfdir to control where HTML and PDF manuals are installed.
> This patch makes the gdb/ directory follow these rather than
> hardcoding its own directory settings.
Thanks.
> * The readline and sim directories need some dummy rules so that these
> targets work at toplevel.
I believe patches to readline need to be sent elsewhere. We just
import their stuff. Maybe sim as well.
> OK to commit?
Yes, but I don't understand why did you need to define docdir in
addition to pdfdir and htmldir. Unlike the other two, docdir is not
used anywhere, so why define it?
Other than that, the patches to files in gdb/doc/ are approved. The
patches to gdb/ directory are fine with me, but I'd like others to
comment on them as well.
next prev parent reply other threads:[~2009-04-17 15:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 11:47 Joseph S. Myers
2009-04-17 15:26 ` Eli Zaretskii [this message]
2009-04-17 15:30 ` Joseph S. Myers
2009-04-17 18:18 ` Eli Zaretskii
2009-04-17 19:43 ` Tom Tromey
2009-04-17 19:49 ` Joseph S. Myers
2009-04-18 7:31 ` Eli Zaretskii
2009-04-18 9:32 ` Joseph S. Myers
2009-04-20 19:51 ` Carlos O'Donell
2009-04-20 20:56 ` Eli Zaretskii
2009-04-21 12:45 ` Joseph S. Myers
2009-04-21 18:54 ` Eli Zaretskii
2009-04-17 15:58 ` Joseph S. Myers
2009-04-17 16:58 ` Tom Tromey
2009-04-17 17:31 ` Daniel Jacobowitz
2009-04-17 18:47 ` Tom Tromey
2009-04-17 19:16 ` 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=83hc0njo9e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.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