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: Fri, 21 Mar 2008 11:38:00 -0000 [thread overview]
Message-ID: <20080321084125.GA77748@adacore.com> (raw)
In-Reply-To: <20080320184605.GH11261@ins.uni-bonn.de>
> Well, maybe, but the filename needs to be embedded (with @setfilename)
> in the input file of makeinfo already, so they really are related.
Right, and as I said, removing the setfilename instructions is fine.
> Alright. I think the patch below does what you want.
>
> Tested 'make info pdf dvi'. OK for trunk? What about 4.3?
OK for trunk, and OK on principle for 4.3. I do not know if you need an OK
from a release manager as well for 4.3.
Thanks for your work and iterations.
Arno
prev parent reply other threads:[~2008-03-21 8:41 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
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 [this message]
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=20080321084125.GA77748@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).