public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] doc: Remove outdated reference to "core" and front-end downloads
@ 2022-11-01 13:59 Jonathan Wakely
  2022-11-09 22:12 ` [PATCH v2] " Jonathan Wakely
  0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Wakely @ 2022-11-01 13:59 UTC (permalink / raw)
  To: gcc-patches

This will just confuse most users, the separate tarballs haven't existed
for years (as already noted elsewhere in install.texi).

OK for trunk?

-- >8 --

gcc/ChangeLog:

	* doc/install.texi: Remove anachronism about separate source
	tarballs.
---
 gcc/doc/install.texi | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index c1876f24a84..e2c397c538a 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3102,9 +3102,7 @@ but it can give you confidence in your new GCC installation or point out
 problems before you install and start using your new GCC@.
 
 First, you must have @uref{download.html,,downloaded the testsuites}.
-These are part of the full distribution, but if you downloaded the
-``core'' compiler plus any front ends, you must download the testsuites
-separately.
+These are included in the source tarball.
 
 Second, you must have the testing tools installed.  This includes
 @uref{https://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
-- 
2.38.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH v2] doc: Remove outdated reference to "core" and front-end downloads
  2022-11-01 13:59 [PATCH] doc: Remove outdated reference to "core" and front-end downloads Jonathan Wakely
@ 2022-11-09 22:12 ` Jonathan Wakely
  2022-11-13  1:27   ` Jeff Law
  0 siblings, 1 reply; 3+ messages in thread
From: Jonathan Wakely @ 2022-11-09 22:12 UTC (permalink / raw)
  To: gcc-patches

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.
---
 gcc/doc/install/testing.rst | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/doc/install/testing.rst b/gcc/doc/install/testing.rst
index 4ae17688440..58d93cc4378 100644
--- a/gcc/doc/install/testing.rst
+++ b/gcc/doc/install/testing.rst
@@ -22,9 +22,7 @@ but it can give you confidence in your new GCC installation or point out
 problems before you install and start using your new GCC.
 
 First, you must have :ref:`downloaded the testsuites <downloading-the-source>`.
-These are part of the full distribution, but if you downloaded the
-'core' compiler plus any front ends, you must download the testsuites
-separately.
+These are included in the source tarball.
 
 Second, you must have the testing tools installed.  This includes
 `DejaGnu <https://www.gnu.org/software/dejagnu/>`_, Tcl, and Expect;
-- 
2.38.1


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] doc: Remove outdated reference to "core" and front-end downloads
  2022-11-09 22:12 ` [PATCH v2] " Jonathan Wakely
@ 2022-11-13  1:27   ` Jeff Law
  0 siblings, 0 replies; 3+ messages in thread
From: Jeff Law @ 2022-11-13  1:27 UTC (permalink / raw)
  To: Jonathan Wakely, gcc-patches


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



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-11-13  1:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-01 13:59 [PATCH] doc: Remove outdated reference to "core" and front-end downloads Jonathan Wakely
2022-11-09 22:12 ` [PATCH v2] " Jonathan Wakely
2022-11-13  1:27   ` Jeff Law

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).