* [PATCH] Clean up references to Subversion in documentation sources.
@ 2020-01-13 16:09 Eric S. Raymond
2020-01-13 16:21 ` Sandra Loosemore
2020-01-15 21:52 ` Jonathan Wakely
0 siblings, 2 replies; 13+ messages in thread
From: Eric S. Raymond @ 2020-01-13 16:09 UTC (permalink / raw)
To: gcc-patches; +Cc: jsm, sandra
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 sensxse, 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.
---
gcc/doc/contribute.texi | 4 +--
gcc/doc/install.texi | 32 ++++++++++---------
libstdc++-v3/doc/xml/faq.xml | 21 +++---------
.../doc/xml/manual/appendix_contributing.xml | 9 ++----
.../doc/xml/manual/status_cxx1998.xml | 2 +-
.../doc/xml/manual/status_cxx2011.xml | 2 +-
.../doc/xml/manual/status_cxx2014.xml | 2 +-
.../doc/xml/manual/status_cxx2017.xml | 2 +-
.../doc/xml/manual/status_cxx2020.xml | 2 +-
libstdc++-v3/doc/xml/manual/status_cxxtr1.xml | 2 +-
.../doc/xml/manual/status_cxxtr24733.xml | 2 +-
11 files changed, 33 insertions(+), 47 deletions(-)
diff --git a/gcc/doc/contribute.texi b/gcc/doc/contribute.texi
index 3c711554419..b0b3b44b6a7 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 e62b3dae545..643f3bb311f 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -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.
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
- <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>
diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index b399e71d482..d2913b1663c 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
@@ -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 >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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
index 2b05ff6601a..cf5722377a6 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
index 6f3551ff65d..9d2de532f3d 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
index a33b4ec1611..a0b900d9a12 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index d154d725391..188c3f88551 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
index a8f0ac294f3..17f28887119 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
index 32ad20a2fb2..b9e415d21ac 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
@@ -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>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
index e8d445116a2..92d892da8ac 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
@@ -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>
--
2.20.1
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:09 [PATCH] Clean up references to Subversion in documentation sources Eric S. Raymond
@ 2020-01-13 16:21 ` Sandra Loosemore
2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:12 ` Jonathan Wakely
2020-01-15 21:52 ` Jonathan Wakely
1 sibling, 2 replies; 13+ messages in thread
From: Sandra Loosemore @ 2020-01-13 16:21 UTC (permalink / raw)
To: Eric S. Raymond, gcc-patches; +Cc: Joseph Myers, libstdc++
On 1/13/20 7:02 AM, Eric S. Raymond wrote:
> Clean up references to SVN in in the GCC docs, redirecting to Git
> documentation as appropriate.
This is OK, although the set of changes for the libstdc++ manual like
this gave me pause:
> diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> index 2b05ff6601a..cf5722377a6 100644
> --- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> +++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
> @@ -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>
IIUC the statements being modified here are incorrect; since the manuals
are packaged with the GCC sources, they go in lock step with the source
version, and the text of the manual describes the GCC version being
built, not mainline. Perhaps the libstdc++ documentation maintainers
would like to correct this separately?
For similar reasons, I suggest backporting this patch to all active GCC
release branches, namely GCC 8 and GCC 9, so that manuals packaged with
upcoming releases from those branches will correctly point to the GIT
repository instead of SVN.
-Sandra
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:21 ` Sandra Loosemore
@ 2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-20 4:40 ` Sandra Loosemore
2020-01-13 17:12 ` Jonathan Wakely
1 sibling, 2 replies; 13+ messages in thread
From: Joseph Myers @ 2020-01-13 16:40 UTC (permalink / raw)
To: Sandra Loosemore; +Cc: Eric S. Raymond, gcc-patches, libstdc++
On Mon, 13 Jan 2020, Sandra Loosemore wrote:
> On 1/13/20 7:02 AM, Eric S. Raymond wrote:
> > Clean up references to SVN in in the GCC docs, redirecting to Git
> > documentation as appropriate.
>
> This is OK, although the set of changes for the libstdc++ manual like this
> gave me pause:
I think you'll need to commit this for Eric (using --author= to set the
git author, whenever you commit a patch for someone else). The libstdc++
maintainers can probably handle regenerating the HTML version of the
libstdc++ documentation.
--
Joseph S. Myers
joseph@codesourcery.com
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:21 ` Sandra Loosemore
2020-01-13 16:40 ` Joseph Myers
@ 2020-01-13 17:12 ` Jonathan Wakely
2020-01-13 17:27 ` Jonathan Wakely
1 sibling, 1 reply; 13+ messages in thread
From: Jonathan Wakely @ 2020-01-13 17:12 UTC (permalink / raw)
To: Sandra Loosemore; +Cc: Eric S. Raymond, gcc-patches, Joseph Myers, libstdc++
On 13/01/20 09:09 -0700, Sandra Loosemore wrote:
>On 1/13/20 7:02 AM, Eric S. Raymond wrote:
>>Clean up references to SVN in in the GCC docs, redirecting to Git
>>documentation as appropriate.
>
>This is OK, although the set of changes for the libstdc++ manual like
>this gave me pause:
>
>>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>index 2b05ff6601a..cf5722377a6 100644
>>--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>@@ -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>
>
>IIUC the statements being modified here are incorrect; since the
>manuals are packaged with the GCC sources, they go in lock step with
>the source version, and the text of the manual describes the GCC
>version being built, not mainline. Perhaps the libstdc++
>documentation maintainers would like to correct this separately?
I did so on the gcc-7 branch, so it says "This page describes the
C++11 support in the GCC 7 series." I have forgotten to do that on the
gcc-8 and gcc-9 branches though, so they lie. I'll do that.
>For similar reasons, I suggest backporting this patch to all active
>GCC release branches, namely GCC 8 and GCC 9, so that manuals packaged
>with upcoming releases from those branches will correctly point to the
>GIT repository instead of SVN.
Agreed.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 17:12 ` Jonathan Wakely
@ 2020-01-13 17:27 ` Jonathan Wakely
2020-01-14 11:46 ` Gerald Pfeifer
0 siblings, 1 reply; 13+ messages in thread
From: Jonathan Wakely @ 2020-01-13 17:27 UTC (permalink / raw)
To: Sandra Loosemore; +Cc: Eric S. Raymond, gcc-patches, Joseph Myers, libstdc++
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
On 13/01/20 16:21 +0000, Jonathan Wakely wrote:
>On 13/01/20 09:09 -0700, Sandra Loosemore wrote:
>>On 1/13/20 7:02 AM, Eric S. Raymond wrote:
>>>Clean up references to SVN in in the GCC docs, redirecting to Git
>>>documentation as appropriate.
>>
>>This is OK, although the set of changes for the libstdc++ manual
>>like this gave me pause:
>>
>>>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>>index 2b05ff6601a..cf5722377a6 100644
>>>--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>>+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>>>@@ -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>
>>
>>IIUC the statements being modified here are incorrect; since the
>>manuals are packaged with the GCC sources, they go in lock step with
>>the source version, and the text of the manual describes the GCC
>>version being built, not mainline. Perhaps the libstdc++
>>documentation maintainers would like to correct this separately?
>
>I did so on the gcc-7 branch, so it says "This page describes the
>C++11 support in the GCC 7 series." I have forgotten to do that on the
>gcc-8 and gcc-9 branches though, so they lie. I'll do that.
Here's what I've committed to releases/gcc-9, I'll do something
similar for gcc-8.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 4640 bytes --]
commit c6f60a62b0b89a0f8c252970f3a4cf0bc2d220ce
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Jan 13 16:25:01 2020 +0000
libstdc++: Fix documentation claiming to refer to mainline
* doc/xml/manual/status_cxx1998.xml: Replace incorrect statement
about documenting mainline.
* 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.
* doc/html/*: Regenerate.
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
index 2b05ff6601a..44a042c2724 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
@@ -18,8 +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
-particular release.
+This page describes the C++ support in the GCC 9 series.
</para>
<!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
index 0fa4bc0dffe..568102823b0 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
@@ -27,8 +27,7 @@ presence of the required flag.
</para>
<para>
-This page describes the C++11 support in mainline GCC SVN, not in any
-particular release.
+This page describes the C++11 support in the GCC 9 series.
</para>
<!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
index a33b4ec1611..7b604307c8e 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
@@ -20,8 +20,7 @@ presence of the required flag.
</para>
<para>
-This page describes the C++14 and library TS support in mainline GCC SVN,
-not in any particular release.
+This page describes the C++14 and library TS support in the GCC 9 series.
</para>
<table frame="all" xml:id="table.cxx14_status">
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 40fe7cd2037..e1513142415 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -20,8 +20,7 @@ presence of the required flag.
</para>
<para>
-This section describes the C++17 and library TS support in mainline GCC SVN,
-not in any particular release.
+This section describes the C++17 and library TS support in the GCC 9 series.
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
index ccf38185a6c..fc7fe0a3d9f 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
@@ -20,8 +20,7 @@ presence of the required flag.
</para>
<para>
-This section describes the C++20 and library TS support in mainline GCC SVN,
-not in any particular release.
+This section describes the C++20 and library TS support in the GCC 9 series.
</para>
<para>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
index 32ad20a2fb2..c1e65752156 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
@@ -22,8 +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
-release.
+This page describes the TR1 support in the GCC 9 series.
</para>
<!-- Status is Yes or No, Broken/Partial-->
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
index e8d445116a2..a3ea8b285f6 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
@@ -16,8 +16,7 @@ decimal floating-point arithmetic
</para>
<para>
-This page describes the TR 24733 support in mainline GCC SVN, not in any
-particular release.
+This page describes the TR 24733 support in the GCC 9 series.
</para>
<!-- Status is Yes or No, Broken/Partial-->
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:40 ` Joseph Myers
@ 2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:06 ` Jonathan Wakely
2020-01-20 4:40 ` Sandra Loosemore
1 sibling, 1 reply; 13+ messages in thread
From: Eric S. Raymond @ 2020-01-13 17:35 UTC (permalink / raw)
To: Joseph Myers; +Cc: Sandra Loosemore, gcc-patches, libstdc++
Joseph Myers <joseph@codesourcery.com>:
> I think you'll need to commit this for Eric (using --author= to set the
> git author, whenever you commit a patch for someone else). The libstdc++
> maintainers can probably handle regenerating the HTML version of the
> libstdc++ documentation.
I'm hesitant to request push access this soon, but...you don't seem to
have an MR capability, and I have some other housekeeping/documentation
patches in mind.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 17:35 ` Eric S. Raymond
@ 2020-01-13 18:06 ` Jonathan Wakely
2020-01-13 18:38 ` Eric S. Raymond
0 siblings, 1 reply; 13+ messages in thread
From: Jonathan Wakely @ 2020-01-13 18:06 UTC (permalink / raw)
To: Eric S. Raymond; +Cc: Joseph Myers, Sandra Loosemore, gcc-patches, libstdc++
On 13/01/20 12:24 -0500, Eric S. Raymond wrote:
>Joseph Myers <joseph@codesourcery.com>:
>> I think you'll need to commit this for Eric (using --author= to set the
>> git author, whenever you commit a patch for someone else). The libstdc++
>> maintainers can probably handle regenerating the HTML version of the
>> libstdc++ documentation.
>
>I'm hesitant to request push access this soon, but...you don't seem to
>have an MR capability, and I have some other housekeeping/documentation
>patches in mind.
Email the patches to gcc-patches@gcc.gnu.org, that's how things get
merged.
We're not looking to change any workflows now.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 18:06 ` Jonathan Wakely
@ 2020-01-13 18:38 ` Eric S. Raymond
2020-01-27 20:11 ` Segher Boessenkool
0 siblings, 1 reply; 13+ messages in thread
From: Eric S. Raymond @ 2020-01-13 18:38 UTC (permalink / raw)
To: Jonathan Wakely; +Cc: Joseph Myers, Sandra Loosemore, gcc-patches, libstdc++
Jonathan Wakely <jwakely@redhat.com>:
> Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> merged.
>
> We're not looking to change any workflows now.
Roger that.
Once the dust from the conversion has settled, though, there is a
related issue I intend to bring up on the main list.
You've only collected about 60% of the potential benefits from git
by adopting git itself. The other 40% would come from moving
to to one of the modern git-centric forges like GitHub or GitLab.
I'm as old-school as any of you guys, so take me seriously when I say
these are not popular for merely faddish reasns. The integration of
repository management, issue tracking, and continuous integration they
offer really does offer a major step up in productivity and
auditability.
I *will* be nudging the GCC project community to think about this.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 17:27 ` Jonathan Wakely
@ 2020-01-14 11:46 ` Gerald Pfeifer
0 siblings, 0 replies; 13+ messages in thread
From: Gerald Pfeifer @ 2020-01-14 11:46 UTC (permalink / raw)
To: Jonathan Wakely
Cc: Sandra Loosemore, Eric S. Raymond, gcc-patches, Joseph Myers, libstdc++
On Mon, 13 Jan 2020, Jonathan Wakely wrote:
> Here's what I've committed to releases/gcc-9, I'll do something
> similar for gcc-8.
Cool, thank you.
That was a good catch, even without the conversion to GIT; I'll
see that I'll contribute to the conversion on the wwwdocs side
over the coming evenings.
Gerald
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:09 [PATCH] Clean up references to Subversion in documentation sources Eric S. Raymond
2020-01-13 16:21 ` Sandra Loosemore
@ 2020-01-15 21:52 ` Jonathan Wakely
1 sibling, 0 replies; 13+ messages in thread
From: Jonathan Wakely @ 2020-01-15 21:52 UTC (permalink / raw)
To: Eric S. Raymond; +Cc: gcc-patches, jsm, sandra
On 13/01/20 09:02 -0500, Eric S. Raymond wrote:
>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
>- <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>.
This makes the text say:
"the up-to-date source , and can be cloned via Git: see [web]."
NACK. Please fix.
> </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>.
I think "Since January 2020 that tool is Git" would be better. It's
unfortunate that all the closed branches will continue to say "at this
time" forever, as it's unclear when that was written.
> </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>.
"For more information see [details]."
> </para>
> </answer>
>diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
>index b399e71d482..d2913b1663c 100644
>--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
>+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
>@@ -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 >NEW</command>;
I don't think that git command is the equivalent of the previous svn
one. I think originally NEW was meant to be the modified file ... but
I'm not really sure. I don't think "git diff > NEW" is very helpful
though.
Also, if you've just done "git pull" then presumably you have a clean
working tree, and "git diff" won't show anything. I think we should
either completely avoid trying to tell people how to produce patches
from git, or should do it right.
The libstdc++ hunks of this patch above are not OK. Please fix the
grammar so the updated text make sense, or leave those bits to me to
fix. Let me know if you want me to do that (and I can also commit the
rest of the patch for you, which Sandra approved).
> else, use <command>diff -cp OLD NEW</command> ... If your
I don't know why we suggest -p here, that *never* shows anything
useful for libstdc++ code. I'll consider fixing that separately
though.
The rest of the libstdc++ changes below are OK to commit.
> 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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>index 2b05ff6601a..cf5722377a6 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxx1998.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
>index 6f3551ff65d..9d2de532f3d 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxx2011.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
>index a33b4ec1611..a0b900d9a12 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxx2014.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
>index d154d725391..188c3f88551 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
>index a8f0ac294f3..17f28887119 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
>index 32ad20a2fb2..b9e415d21ac 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
>@@ -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>
>
>diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
>index e8d445116a2..92d892da8ac 100644
>--- a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
>+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
>@@ -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>
>
>--
>2.20.1
>
>
>--
> <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
@ 2020-01-20 4:40 ` Sandra Loosemore
2020-01-20 23:05 ` Jonathan Wakely
1 sibling, 1 reply; 13+ messages in thread
From: Sandra Loosemore @ 2020-01-20 4:40 UTC (permalink / raw)
To: Joseph Myers; +Cc: Eric S. Raymond, gcc-patches, libstdc++
On 1/13/20 9:12 AM, Joseph Myers wrote:
> On Mon, 13 Jan 2020, Sandra Loosemore wrote:
>
>> On 1/13/20 7:02 AM, Eric S. Raymond wrote:
>>> Clean up references to SVN in in the GCC docs, redirecting to Git
>>> documentation as appropriate.
>>
>> This is OK, although the set of changes for the libstdc++ manual like this
>> gave me pause:
>
> I think you'll need to commit this for Eric (using --author= to set the
> git author, whenever you commit a patch for someone else). The libstdc++
> maintainers can probably handle regenerating the HTML version of the
> libstdc++ documentation.
I've pushed this patch to mainline and the gcc8 and gcc9 branches now.
-Sandra
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-20 4:40 ` Sandra Loosemore
@ 2020-01-20 23:05 ` Jonathan Wakely
0 siblings, 0 replies; 13+ messages in thread
From: Jonathan Wakely @ 2020-01-20 23:05 UTC (permalink / raw)
To: Sandra Loosemore; +Cc: Joseph Myers, Eric S. Raymond, gcc-patches, libstdc++
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On 19/01/20 20:06 -0700, Sandra Loosemore wrote:
>On 1/13/20 9:12 AM, Joseph Myers wrote:
>>On Mon, 13 Jan 2020, Sandra Loosemore wrote:
>>
>>>On 1/13/20 7:02 AM, Eric S. Raymond wrote:
>>>>Clean up references to SVN in in the GCC docs, redirecting to Git
>>>>documentation as appropriate.
>>>
>>>This is OK, although the set of changes for the libstdc++ manual like this
>>>gave me pause:
>>
>>I think you'll need to commit this for Eric (using --author= to set the
>>git author, whenever you commit a patch for someone else). The libstdc++
>>maintainers can probably handle regenerating the HTML version of the
>>libstdc++ documentation.
>
>I've pushed this patch to mainline and the gcc8 and gcc9 branches now.
This fixes the broken grammar in the patch. Committed to trunk so far,
I'll backport it too.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 3497 bytes --]
commit c784f1620498f78cfb9075a4696f2813722eb547
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Jan 20 20:37:52 2020 +0000
libstdc++: Fix recent documentation changes
* doc/xml/faq.xml: Fix grammar.
* doc/xml/manual/appendix_contributing.xml: Improve instructions.
* doc/xml/manual/spine.xml: Update copyright years.
* doc/html/*: Regenerate.
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 21c312dce35..aff6c8d6004 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -34,8 +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 , 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>.
+ bleeding-edge code, the up-to-date source can be cloned via
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">Git</link>.
</para>
<para>
@@ -295,15 +295,11 @@
download sites</link> is provided on the main GCC site.
</para>
<para>
- 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>Git</application>.
- </para>
- <para>
- For more information
- see <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">
- details</link>.
+ Current libstdc++ sources can always be found in the main GCC source
+ repository, available using the appropriate version control tool.
+ At this time, that tool is <application>Git</application>.
+ For more details see the documentation on
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/git.html">using the Git repository</link>.
</para>
</answer>
</qandaentry>
diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index d2913b1663c..79fa0ed32b8 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
@@ -170,9 +170,10 @@
<listitem>
<para>
- The patch itself. If you are accessing the Git
- repository use <command>git pull; git diff >NEW</command>;
- else, use <command>diff -cp OLD NEW</command> ... If your
+ The patch itself. If you are using the Git repository use
+ <command>git diff</command> or <command>git format-patch</command>
+ to produce a patch;
+ otherwise, 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.
</para>
diff --git a/libstdc++-v3/doc/xml/manual/spine.xml b/libstdc++-v3/doc/xml/manual/spine.xml
index a2cc1294e73..4db3037ac4d 100644
--- a/libstdc++-v3/doc/xml/manual/spine.xml
+++ b/libstdc++-v3/doc/xml/manual/spine.xml
@@ -27,6 +27,7 @@
<year>2017</year>
<year>2018</year>
<year>2019</year>
+ <year>2020</year>
<holder>
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://www.fsf.org">FSF</link>
</holder>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [PATCH] Clean up references to Subversion in documentation sources.
2020-01-13 18:38 ` Eric S. Raymond
@ 2020-01-27 20:11 ` Segher Boessenkool
0 siblings, 0 replies; 13+ messages in thread
From: Segher Boessenkool @ 2020-01-27 20:11 UTC (permalink / raw)
To: Eric S. Raymond
Cc: Jonathan Wakely, Joseph Myers, Sandra Loosemore, gcc-patches, libstdc++
On Mon, Jan 13, 2020 at 01:12:15PM -0500, Eric S. Raymond wrote:
> Jonathan Wakely <jwakely@redhat.com>:
> > Email the patches to gcc-patches@gcc.gnu.org, that's how things get
> > merged.
> >
> > We're not looking to change any workflows now.
>
> Roger that.
>
> Once the dust from the conversion has settled, though, there is a
> related issue I intend to bring up on the main list.
>
> You've only collected about 60% of the potential benefits from git
> by adopting git itself. The other 40% would come from moving
> to to one of the modern git-centric forges like GitHub or GitLab.
NAK.
Our development model fits our needs well, even with all its warts.
A "pull request" model would not fit well *at all*.
The "everything passes through email" model is *good*, not in the least
because it puts everyone on a level playing field. Everyone can see
everything, and comment on everything.
And if it slows you down, well, that is a good thing as well probably!
Thought and carefulness and looking at things from multiple angles is
what we need, not raw speed: we need good changes, we do not need making
it easier to get your changes included at the cost of basic quality.
Anyway, 90% of the advantages of using Git come from using it *locally*,
which many of us have been doing since forever and a day already.
Segher
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2020-01-27 19:33 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-13 16:09 [PATCH] Clean up references to Subversion in documentation sources Eric S. Raymond
2020-01-13 16:21 ` Sandra Loosemore
2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:06 ` Jonathan Wakely
2020-01-13 18:38 ` Eric S. Raymond
2020-01-27 20:11 ` Segher Boessenkool
2020-01-20 4:40 ` Sandra Loosemore
2020-01-20 23:05 ` Jonathan Wakely
2020-01-13 17:12 ` Jonathan Wakely
2020-01-13 17:27 ` Jonathan Wakely
2020-01-14 11:46 ` Gerald Pfeifer
2020-01-15 21:52 ` Jonathan Wakely
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).