From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2181) id 8A5373858417; Mon, 18 Mar 2024 14:03:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8A5373858417 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1710770611; bh=H3CrCxEmKTaFVanR8GZWLV+W+fYmSqzpbcw43YrD9+M=; h=From:To:Subject:Date:From; b=GdgUpBiul3Cltm+sSywiWs0r1geplY/whaMuaeg0uq6/JByXd5GDei8e3ubUk4j+1 BF18xfRrb9+49TqbzfGGdQAUEi0lyxthCkHKirYwB+keXFqz5wHYzk2M1C1ZvoPZUu myOy8xgqmEze80OEUhV1nTyQFjO83iWHGMnaHOvA= MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" From: Jonathan Wakely To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-10223] libstdc++: Update outdated docs on contributing X-Act-Checkin: gcc X-Git-Author: Jonathan Wakely X-Git-Refname: refs/heads/releases/gcc-12 X-Git-Oldrev: d9076dafa12c93e96b349035fb59050151403866 X-Git-Newrev: 57f4c935f915454879a0d13f0319ba09c9c01309 Message-Id: <20240318140331.8A5373858417@sourceware.org> Date: Mon, 18 Mar 2024 14:03:31 +0000 (GMT) List-Id: https://gcc.gnu.org/g:57f4c935f915454879a0d13f0319ba09c9c01309 commit r12-10223-g57f4c935f915454879a0d13f0319ba09c9c01309 Author: Jonathan Wakely Date: Wed Feb 28 11:24:47 2024 +0000 libstdc++: Update outdated docs on contributing We don't want a separate ChangeLog submission now. libstdc++-v3/ChangeLog: * doc/xml/manual/appendix_contributing.xml: Replace outdated info on ChangeLog entries. * doc/html/manual/appendix_contributing.html: Regenerate. (cherry picked from commit 7c7c937b5e71cf2b53f462cfa6a1df39b5538cee) Diff: --- libstdc++-v3/doc/html/manual/appendix_contributing.html | 16 +++++++++------- libstdc++-v3/doc/xml/manual/appendix_contributing.xml | 16 +++++++++------- 2 files changed, 18 insertions(+), 14 deletions(-) diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index 8be678eb919..2d04cadd4e8 100644 --- a/libstdc++-v3/doc/html/manual/appendix_contributing.html +++ b/libstdc++-v3/doc/html/manual/appendix_contributing.html @@ -79,19 +79,19 @@ bug. For new features a description of the feature and your implementation.

  • - A ChangeLog entry as plain text; see the various - ChangeLog files for format and content. If you are - using emacs as your editor, simply position the insertion - point at the beginning of your change and hit CX-4a to bring - up the appropriate ChangeLog entry. See--magic! Similar - functionality also exists for vi. + A ChangeLog entry as part of the Git commit message. Check + some recent commits for format and content. The + contrib/mklog.py script can be used to + generate a ChangeLog template for commit messages. See + Read-write Git access + for scripts and aliases that are useful here.

  • A testsuite submission or sample program that will easily and simply show the existing error or test new functionality.

  • The patch itself. If you are using the Git repository use - git diff or git format-patch + git show or git format-patch to produce a patch; otherwise, use diff -cp OLD NEW. If your version of diff does not support these options, then get the @@ -102,6 +102,8 @@ patches and related discussion should be sent to the libstdc++ mailing list. In common with the rest of GCC, patches should also be sent to the gcc-patches mailing list. + So you could send your email To:libstdc++@gcc.gnu.org and + Cc:gcc-patches@gcc.gnu.org for example.

    • Prev Up Next
    Part IV.  Appendices  Home Directory Layout and Source Conventions
    \ No newline at end of file diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml index ceb21f4478a..074baf0fb4d 100644 --- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml +++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml @@ -151,12 +151,12 @@ - A ChangeLog entry as plain text; see the various - ChangeLog files for format and content. If you are - using emacs as your editor, simply position the insertion - point at the beginning of your change and hit CX-4a to bring - up the appropriate ChangeLog entry. See--magic! Similar - functionality also exists for vi. + A ChangeLog entry as part of the Git commit message. Check + some recent commits for format and content. The + contrib/mklog.py script can be used to + generate a ChangeLog template for commit messages. See + Read-write Git access + for scripts and aliases that are useful here. @@ -171,7 +171,7 @@ The patch itself. If you are using the Git repository use - git diff or git format-patch + git show or git format-patch to produce a patch; otherwise, use diff -cp OLD NEW. If your version of diff does not support these options, then get the @@ -186,6 +186,8 @@ patches and related discussion should be sent to the libstdc++ mailing list. In common with the rest of GCC, patches should also be sent to the gcc-patches mailing list. + So you could send your email To:libstdc++@gcc.gnu.org and + Cc:gcc-patches@gcc.gnu.org for example.