OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clean up references to Subversion in documentation sources.

Browse Source 
Clean up references to SVN in in the GCC docs, redirecting to Git
documentation as appropriate.

Where references to "the source code repository" rather than a
specific VCS make sense, I have used them. You might, after
all, change VCSes again someday.

I have not modified either generated HTML files nor maintainer scripts.
These changes should be complete with repect to the documentation tree.

2020-01-19  Eric S. Raymond <esr@thyrsus.com>

	gcc/
	* doc/contribute.texi: Update for SVN -> Git transition.
	* doc/install.texi: Likewise.

	libstdc++-v3
	* doc/xml/faq.xml: Update for SVN -> Git transition.
	* doc/xml/manual/appendix_contributing.xml: Likewise.
	* doc/xml/manual/status_cxx1998.xml: Likewise.
	* doc/xml/manual/status_cxx2011.xml: Likewise.
	* doc/xml/manual/status_cxx2014.xml: Likewise.
	* doc/xml/manual/status_cxx2017.xml: Likewise.
	* doc/xml/manual/status_cxx2020.xml: Likewise.
	* doc/xml/manual/status_cxxtr1.xml: Likewise.
	* doc/xml/manual/status_cxxtr24733.xml: Likewise.
This commit is contained in:
Eric S. Raymond 2020-01-19 17:12:29 -08:00 committed by Sandra Loosemore
parent 8863f61c9c
commit f4d83eba60
13 changed files with 50 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
2020-01-19 Eric S. Raymond <esr@thyrsus.com>
* doc/contribute.texi: Update for SVN -> Git transition.
* doc/install.texi: Likewise.
2020-01-18 Jan Hubicka <hubicka@ucw.cz>
PR lto/93318

4
gcc/doc/contribute.texi
View File

@ -6,8 +6,8 @@
@chapter Contributing to GCC Development
If you would like to help pretest GCC releases to assure they work well,
current development sources are available by SVN (see
@uref{http://gcc.gnu.org/svn.html}). Source and binary snapshots are
current development sources are available via Git (see
@uref{http://gcc.gnu.org/git.html}). Source and binary snapshots are
also available for FTP; see @uref{http://gcc.gnu.org/snapshots.html}.
If you would like to work on improvements to GCC, please read the

32
gcc/doc/install.texi
View File

@ -356,8 +356,9 @@ and up works.
Necessary when regenerating @file{Makefile} dependencies in libiberty.
Necessary when regenerating @file{libiberty/functions.texi}.
Necessary when generating manpages from Texinfo manuals.
Used by various scripts to generate some files included in SVN (mainly
Unicode-related and rarely changing) from source tables.
Used by various scripts to generate some files included in the source
repository (mainly Unicode-related and rarely changing) from source
tables.
Used by @command{automake}.
@ -482,8 +483,8 @@ Necessary to regenerate the top level @file{Makefile.in} file from
Necessary when modifying @file{*.l} files.
Necessary to build GCC during development because the generated output
files are not included in the SVN repository. They are included in
releases.
files are not included in the version-controlled source repository.
They are included in releases.
@item Texinfo version 4.7 (or later)
@ -495,7 +496,7 @@ create printable documentation in DVI or PDF format. Texinfo version
4.8 or later is required for @command{make pdf}.
Necessary to build GCC documentation during development because the
generated output files are not included in the SVN repository. They are
generated output files are not included in the repository. They are
included in releases.
@item @TeX{} (any working version)
@ -509,10 +510,10 @@ DVI or PDF files, respectively.
Necessary to regenerate @file{jit/docs/_build/texinfo} from the @file{.rst}
files in the directories below @file{jit/docs}.
@item SVN (any version)
@item git (any version)
@itemx SSH (any version)
Necessary to access the SVN repository. Public releases and weekly
Necessary to access the source repository. Public releases and weekly
snapshots of the development sources are also available via HTTPS@.
@item GNU diffutils version 2.7 (or later)
@ -547,7 +548,7 @@ own sources.
@cindex Downloading GCC
@cindex Downloading the Source
GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and via
GCC is distributed via @uref{http://gcc.gnu.org/git.html,,git} and via
HTTPS as tarballs compressed with @command{gzip} or @command{bzip2}.
Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
@ -606,9 +607,10 @@ for both native and cross targets.
We use @var{srcdir} to refer to the toplevel source directory for
GCC; we use @var{objdir} to refer to the toplevel build/object directory.
If you obtained the sources via SVN, @var{srcdir} must refer to the top
@file{gcc} directory, the one where the @file{MAINTAINERS} file can be
found, and not its @file{gcc} subdirectory, otherwise the build will fail.
If you obtained the sources by cloning the repository, @var{srcdir}
must refer to the top @file{gcc} directory, the one where the
@file{MAINTAINERS} file can be found, and not its @file{gcc}
subdirectory, otherwise the build will fail.
If either @var{srcdir} or @var{objdir} is located on an automounted NFS
file system, the shell's built-in @command{pwd} command will return
@ -1543,7 +1545,7 @@ with @option{--enable-bootstrap}.
@item --enable-generated-files-in-srcdir
Neither the .c and .h files that are generated from Bison and flex nor the
info manuals and man pages that are built from the .texi files are present
in the SVN development tree. When building GCC from that development tree,
in the repository development tree. When building GCC from that development tree,
or from one of our snapshots, those generated files are placed in your
build directory, which allows for the source to be in a readonly
directory.
@ -1843,7 +1845,7 @@ consistency checks of the requested complexity. This does not change the
generated code, but adds error checking within the compiler. This will
slow down the compiler and may only work properly if you are building
the compiler with GCC@. This is @samp{yes,extra} by default when building
from SVN or snapshots, but @samp{release} for releases. The default
from the source repository or snapshots, but @samp{release} for releases. The default
for building the stage1 compiler is @samp{yes}. More control
over the checks may be had by specifying @var{list}. The categories of
checks available are @samp{yes} (most common checks
@ -2495,7 +2497,7 @@ that type mismatches occur, this could be the cause.
The solution is not to use such a directory for building GCC@.
Similarly, when building from SVN or snapshots, or if you modify
Similarly, when building from the source repository or snapshots, or if you modify
@file{*.l} files, you need the Flex lexical analyzer generator
installed. If you do not modify @file{*.l} files, releases contain
the Flex-generated files and you do not need Flex installed to build
@ -2503,7 +2505,7 @@ them. There is still one Flex-based lexical analyzer (part of the
build machinery, not of GCC itself) that is used even if you only
build the C front end.
When building from SVN or snapshots, or if you modify Texinfo
When building from the source repository or snapshots, or if you modify Texinfo
documentation, you need version 4.7 or later of Texinfo installed if you
want Info documentation to be regenerated. Releases contain Info
documentation pre-built for the unmodified documentation in the release.

12
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,15 @@
2020-01-19 Eric S. Raymond <esr@thyrsus.com>
* doc/xml/faq.xml: Update for SVN -> Git transition.
* doc/xml/manual/appendix_contributing.xml: Likewise.
* doc/xml/manual/status_cxx1998.xml: Likewise.
* doc/xml/manual/status_cxx2011.xml: Likewise.
* doc/xml/manual/status_cxx2014.xml: Likewise.
* doc/xml/manual/status_cxx2017.xml: Likewise.
* doc/xml/manual/status_cxx2020.xml: Likewise.
* doc/xml/manual/status_cxxtr1.xml: Likewise.
* doc/xml/manual/status_cxxtr24733.xml: Likewise.
2020-01-18 Iain Sandoe <iain@sandoe.co.uk>
* include/Makefile.am: Add coroutine to the std set.

21
libstdc++-v3/doc/xml/faq.xml
View File

@ -34,9 +34,8 @@
clauses 20 through 33 and annex D (prior to the 2017 standard
the library clauses started with 17). For those who want to see
exactly how far the project has come, or just want the latest
bleeding-edge code, the up-to-date source is available over
anonymous SVN, and can be browsed over the
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/svn.html">web</link>.
bleeding-edge code, the up-to-date source , and can be cloned via Git: see
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">web</link>.
</para>
<para>
@ -299,23 +298,11 @@
Current libstdc++ sources can always be checked out of the main
GCC source repository using the appropriate version control
tool. At this time, that tool
is <application>Subversion</application>.
is <application>Git</application>.
</para>
<para>
<application>Subversion</application>, or <acronym>SVN</acronym>, is
one of several revision control packages. It was selected for GNU
projects because it's free (speech), free (beer), and very high
quality. The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://subversion.tigris.org"> Subversion
home page</link> has a better description.
</para>
<para>
The <quote>anonymous client checkout</quote> feature of SVN is
similar to anonymous FTP in that it allows anyone to retrieve
the latest libstdc++ sources.
</para>
<para>
For more information
see <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/svn.html"><acronym>SVN</acronym>
see <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">
details</link>.
</para>
</answer>

9
libstdc++-v3/doc/xml/manual/appendix_contributing.xml
View File

@ -170,14 +170,11 @@
<listitem>
<para>
The patch itself. If you are accessing the SVN
repository use <command>svn update; svn diff NEW</command>;
The patch itself. If you are accessing the Git
repository use <command>git pull; git diff &gt;NEW</command>;
else, use <command>diff -cp OLD NEW</command> ... If your
version of diff does not support these options, then get the
latest version of GNU
diff. The <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/wiki/SvnTricks">SVN
Tricks</link> wiki page has information on customising the
output of <code>svn diff</code>.
latest version of GNU diff.
</para>
</listitem>

2
libstdc++-v3/doc/xml/manual/status_cxx1998.xml
View File

@ -18,7 +18,7 @@ This status table is based on the table of contents of ISO/IEC 14882:2003.
</para>
<para>
This page describes the C++ support in mainline GCC SVN, not in any
This page describes the C++ support in mainline GCC, not in any
particular release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxx2011.xml
View File

@ -27,7 +27,7 @@ presence of the required flag.
</para>
<para>
This page describes the C++11 support in mainline GCC SVN, not in any
This page describes the C++11 support in mainline GCC, not in any
particular release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxx2014.xml
View File

@ -20,7 +20,7 @@ presence of the required flag.
</para>
<para>
This page describes the C++14 and library TS support in mainline GCC SVN,
This page describes the C++14 and library TS support in mainline GCC,
not in any particular release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxx2017.xml
View File

@ -20,7 +20,7 @@ presence of the required flag.
</para>
<para>
This section describes the C++17 and library TS support in mainline GCC SVN,
This section describes the C++17 and library TS support in mainline GCC,
not in any particular release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxx2020.xml
View File

@ -20,7 +20,7 @@ presence of the required flag.
</para>
<para>
This section describes the C++20 and library TS support in mainline GCC SVN,
This section describes the C++20 and library TS support in mainline GCC,
not in any particular release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
View File

@ -22,7 +22,7 @@ In this implementation the header names are prefixed by
</para>
<para>
This page describes the TR1 support in mainline GCC SVN, not in any particular
This page describes the TR1 support in mainline GCC, not in any particular
release.
</para>

2
libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
View File

@ -16,7 +16,7 @@ decimal floating-point arithmetic
</para>
<para>
This page describes the TR 24733 support in mainline GCC SVN, not in any
This page describes the TR 24733 support in mainline GCC, not in any
particular release.
</para>