diff --git a/libstdc++-v3/doc/html/manual/appendix_contributing.html b/libstdc++-v3/doc/html/manual/appendix_contributing.html index e0b253ad263..cd2c1e153d7 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 a9196493adc..0dcafcb98af 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.