From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2153) id 4DB68386197D; Thu, 17 Sep 2020 16:35:58 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4DB68386197D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1600360558; bh=bs50RngXBRNwUA4/7ITcjFb58xTZC8G4PRRC0rNNR/Q=; h=From:To:Subject:Date:From; b=paMHTxgFBP2E8BMHUt2s+i/bC/XQXeexbaP4/J39WwFf1/aJAciQRHR0vVEmfn4RS ghVpUZVDXLXJqXRS0H6KLlwHwdVRCdyKN2DGbCBZQoXsQr3HQFiP8UfmF2dixLUkkK 7rOG3jBIgl80DQfsBLUPOz12v3FpZlqJcdShnCqk= Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jakub Jelinek To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] Clean up references to Subversion in documentation sources. X-Act-Checkin: gcc X-Git-Author: Eric S. Raymond X-Git-Refname: refs/vendors/redhat/heads/gcc-8-branch X-Git-Oldrev: 56fcd14d374d726f0b4a99b4b85b8ee595ca7cde X-Git-Newrev: e53354eb6ccffb0ecda969e0fb2fdbe32f41d7e0 Message-Id: <20200917163558.4DB68386197D@sourceware.org> Date: Thu, 17 Sep 2020 16:35:58 +0000 (GMT) X-BeenThere: libstdc++-cvs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2020 16:35:58 -0000 https://gcc.gnu.org/g:e53354eb6ccffb0ecda969e0fb2fdbe32f41d7e0 commit e53354eb6ccffb0ecda969e0fb2fdbe32f41d7e0 Author: Eric S. Raymond Date: Sun Jan 19 18:40:45 2020 -0800 Clean up references to Subversion in documentation sources. 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 Sandra Loosemore Partial backport from mainline: 2020-01-19 Eric S. Raymond 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. Diff: --- gcc/ChangeLog | 10 ++++++ gcc/doc/contribute.texi | 4 +-- gcc/doc/install.texi | 37 +++++++++++----------- libstdc++-v3/ChangeLog | 9 ++++++ libstdc++-v3/doc/xml/faq.xml | 21 +++--------- .../doc/xml/manual/appendix_contributing.xml | 9 ++---- 6 files changed, 47 insertions(+), 43 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 70f8702bf07..03df25986b5 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,13 @@ +2020-01-19 Eric S. Raymond + Sandra Loosemore + + Backport from mainline: + + 2020-01-19 Eric S. Raymond + + * doc/contribute.texi: Update for SVN -> Git transition. + * doc/install.texi: Likewise. + 2020-01-15 Martin Liska Backport from mainline diff --git a/gcc/doc/contribute.texi b/gcc/doc/contribute.texi index 7ade11686f9..3bef1f29efe 100644 --- a/gcc/doc/contribute.texi +++ b/gcc/doc/contribute.texi @@ -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 diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 1cc427249a4..b8e7185f781 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -335,8 +335,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}. @@ -461,8 +462,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) @@ -474,7 +475,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) @@ -488,11 +489,11 @@ 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 -snapshots of the development sources are also available via FTP@. +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) @@ -526,9 +527,8 @@ own sources. @cindex Downloading GCC @cindex Downloading the Source -GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP -tarballs compressed with @command{gzip} or -@command{bzip2}. +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} for information on how to obtain GCC@. @@ -586,9 +586,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 @@ -1476,7 +1477,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. @@ -1768,7 +1769,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 @@ -2345,7 +2346,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 @@ -2353,7 +2354,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. diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index e2855b87657..bf3886867a9 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,12 @@ +2020-01-19 Eric S. Raymond + Sandra Loosemore + + Partial backport from mainline: + + 2020-01-19 Eric S. Raymond + * doc/xml/faq.xml: Update for SVN -> Git transition. + * doc/xml/manual/appendix_contributing.xml: Likewise. + 2020-01-13 Jonathan Wakely * doc/xml/manual/status_cxx1998.xml: Replace incorrect statement diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml index b4bf333e26a..21c312dce35 100644 --- a/libstdc++-v3/doc/xml/faq.xml +++ b/libstdc++-v3/doc/xml/faq.xml @@ -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 - web. + bleeding-edge code, the up-to-date source , and can be cloned via Git: see + web. @@ -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 Subversion. + is Git. - Subversion, or SVN, 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 Subversion - home page has a better description. - - - The anonymous client checkout feature of SVN is - similar to anonymous FTP in that it allows anyone to retrieve - the latest libstdc++ sources. - - For more information - see SVN + see details. diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml index 41335475f3b..a049d7d91ad 100644 --- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml +++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml @@ -170,14 +170,11 @@ - The patch itself. If you are accessing the SVN - repository use svn update; svn diff NEW; + The patch itself. If you are accessing the Git + repository use git pull; git diff >NEW; else, use diff -cp OLD NEW ... If your version of diff does not support these options, then get the - latest version of GNU - diff. The SVN - Tricks wiki page has information on customising the - output of svn diff. + latest version of GNU diff.