From: Jeff Law <jeffreyalaw@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] doc: Remove outdated reference to "core" and front-end downloads
Date: Sat, 12 Nov 2022 18:27:23 -0700 [thread overview]
Message-ID: <056a408d-9fab-2ba5-7d9a-083b75e8c726@gmail.com> (raw)
In-Reply-To: <20221109221205.61966-1-jwakely@redhat.com>
On 11/9/22 15:12, Jonathan Wakely via Gcc-patches wrote:
> Patch rebased on the new doc format. I haven't tested building the docs
> this way, but this is just plain text here.
>
> OK for trunk?
>
> -- >8 --
>
> gcc/ChangeLog:
>
> * doc/install/testing.rst: Remove anachronism about separate
> source tarballs.
OK.
jeff
prev parent reply other threads:[~2022-11-13 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:59 [PATCH] " Jonathan Wakely
2022-11-09 22:12 ` [PATCH v2] " Jonathan Wakely
2022-11-13 1:27 ` Jeff Law [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=056a408d-9fab-2ba5-7d9a-083b75e8c726@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).