From: Arnaud Charlet <charlet@adacore.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, ADA, DOC] PR 15479: Crossrefs and links
Date: Mon, 17 Mar 2008 09:47:00 -0000 [thread overview]
Message-ID: <20080317075928.GA90987@adacore.com> (raw)
In-Reply-To: <20080316220220.GA3899@ins.uni-bonn.de>
> OK. In the patch below I did that. However, for now I did not to
> rename the output file to gnat_rm_{unw,vms}. Please say so if you want
> that, too.
No, I do not want that, and do not want such handling for gnat_rm.texi
> OK for trunk and 4.3?
Not in the proposed form I'm afraid, see below.
> gcc/ada/ChangeLog:
> 2008-03-16 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
>
> PR documentation/15479
> * gnat_ugn.texi: Fix cross references to the GNAT Reference
> Manual. Convert links to the GCC, GDB, Emacs, and GNU make
> manuals to be proper texinfo links.
> * gnat_rm.texi: Fix cross references to the GNAT User's Guide.
> * Make-lang.in (doc/gnat_rm.texi): New, create from
> ada/gnat_rm.texi using xgnatugn.
Well, I'd rather not have to preprocess gnat_rm.texi, that's a heavy
solution.
There have to be a simpler solution here, such as using a texi
variable for example.
Arno
next prev parent reply other threads:[~2008-03-17 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 14:12 Ralf Wildenhues
2008-03-16 18:32 ` Arnaud Charlet
2008-03-16 22:08 ` Ralf Wildenhues
2008-03-17 9:47 ` Arnaud Charlet [this message]
2008-03-17 20:56 ` Ralf Wildenhues
2008-03-18 9:05 ` Arnaud Charlet
2008-03-18 21:55 ` Ralf Wildenhues
2008-03-18 22:05 ` Arnaud Charlet
2008-03-18 22:27 ` Ralf Wildenhues
2008-03-19 8:44 ` Arnaud Charlet
2008-03-20 19:58 ` Ralf Wildenhues
2008-03-21 11:38 ` Arnaud Charlet
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=20080317075928.GA90987@adacore.com \
--to=charlet@adacore.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.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).