From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [BUG] README: Reference to non-existent path?
Date: Mon, 14 Nov 2022 15:36:19 +0000 [thread overview]
Message-ID: <CAH6eHdR4t8VvLrSz1g9R65_L-6kje5XQ_9A7RMPJ+H-fUAriog@mail.gmail.com> (raw)
In-Reply-To: <d3db7bbf-fc05-618d-51c8-cdecbbeab081@gmail.com>
On Mon, 14 Nov 2022 at 15:03, Alejandro Colomar wrote:
> BTW, it might be interesting to provide that manual
> in a package, so that I could install it as something like:
>
> apt-get install gcc-doc-internal
"info gccint" already works fine on my distro. If it's not packaged
for yours, that's a distro issue.
next prev parent reply other threads:[~2022-11-14 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 15:02 Alejandro Colomar
2022-11-14 15:32 ` Jonathan Wakely
2022-11-14 15:36 ` Jonathan Wakely [this message]
2022-11-14 17:00 ` Alejandro Colomar
2022-11-14 18:24 ` Joseph Myers
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=CAH6eHdR4t8VvLrSz1g9R65_L-6kje5XQ_9A7RMPJ+H-fUAriog@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=gcc@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).