From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2142) id EFCE53851C08; Sun, 31 May 2020 21:51:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EFCE53851C08 To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 20bb60460321e98a961d992618550751188036fd X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: 6e86d16b187fc42700b3f1298b68dd89db02c025 X-Git-Newrev: 20bb60460321e98a961d992618550751188036fd Message-Id: <20200531215156.EFCE53851C08@sourceware.org> Date: Sun, 31 May 2020 21:51:56 +0000 (GMT) From: Gerald Pfeifer X-BeenThere: gcc-cvs-wwwdocs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-cvs-wwwdocs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 May 2020 21:51:57 -0000 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 20bb60460321e98a961d992618550751188036fd (commit) from 6e86d16b187fc42700b3f1298b68dd89db02c025 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 20bb60460321e98a961d992618550751188036fd Author: Gerald Pfeifer Date: Sun May 31 23:51:01 2020 +0200 Simplify language in gitwrite.html. diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index e5dccd8e..36bb1a20 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -39,12 +39,11 @@ is not sufficient).

If you already have an account on sourceware.org / gcc.gnu.org, ask overseers@gcc.gnu.org to add access to the GCC repository. Include the name of your sponsor and CC: her. -If you do not have an account yet, use this form, again specifying your sponsor.

-

We will then provision you on -gcc.gnu.org and inform you by mail. At this point, +

We will then provision you and inform you by mail. At this point, check out a tree using the instructions below and add yourself to the MAINTAINERS file. Note: Your first and last names must be exactly the same between your account on gcc.gnu.org and the @@ -61,8 +60,7 @@ access policies below.

Setting up your local Git tree

-

Once your account has been set up, check out the GCC sources by -issuing the command:

+

Check out the GCC sources by issuing the command:

git clone git+ssh://username@gcc.gnu.org/git/gcc.git gcc @@ -99,7 +97,7 @@ git config --global user.email "Your Email Address"

If you wish to use a different name or email address for GCC commits from that in $HOME/.gitconfig, you can configure -that in an individual Git tree using a similar command +that in an individual Git tree using similar invocations without --global.

@@ -241,16 +239,15 @@ automatically added to the corresponding ChangeLog files based on the git commit message. See the documentation of ChangeLog format. -
  • Make sure to rebuild any generated files that would be affected by -the patch. Make sure to check them in along with the files explicitly -modified by the patch.
    • +
  • Make sure to rebuild any generated files affected by +the patch and commit them with the files explicitly modified.
  • If the patch adds any new files, such as testcases, use git add to make Git aware of them.
  • We recommend using "git diff HEAD" after applying a patch to a local tree. Review the output to make sure that only the -changes you wanted to check in will be checked in. Also check to see +changes you want will be checked in. Also see if the copyright dates need to be updated.
  • Use "git commit" to check in the patch; either name @@ -317,7 +314,7 @@ other developers, you can use git push as follows:

    git push origin $BRANCH:devel/$BRANCH
    • -

    Also, please document such branches at the +

    Please document such branches at the list of development branches.

    @@ -450,9 +447,8 @@ much the same way as C function names are used).

    contrib/git-fetch-vendor.sh

    -

    Vendor spaces are controlled by the named vendor. Unless you are -affiliated with that vendor, do not push changes to that space without -their express permission.

    +

    Vendor spaces are controlled by the named vendor. Do not push +changes to that space without their express permission.

    This script will set up a new 'remote' that can be used to access the area used by a named vendor. You need to ----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 24 ++++++++++-------------- 1 file changed, 10 insertions(+), 14 deletions(-) hooks/post-receive -- gcc-wwwdocs