gcc-wwwdocs branch master updated. 20bb60460321e98a961d992618550751188036fd

gcc-wwwdocs branch master updated. 20bb60460321e98a961d992618550751188036fd

[Gerald Pfeifer]

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 <gerald@pfeifer.com>
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).</p>
 <p>If you already have an account on sourceware.org / gcc.gnu.org, ask
 <code>overseers@gcc.gnu.org</code> 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 <a
+Otherwise use <a
 href="https://sourceware.org/cgi-bin/pdw/ps_form.cgi">this form</a>,
 again specifying your sponsor.</p>
 
-<p>We will then provision you on  
-<code>gcc.gnu.org</code> and inform you by mail. At this point,
+<p>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 <em>must</em>
 be exactly the same between your account on gcc.gnu.org and the
@@ -61,8 +60,7 @@ access policies below.</p>
 <hr />
 <h2 id="setup">Setting up your local Git tree</h2>
 
-<p>Once your account has been set up, check out the GCC sources by 
-issuing the command:</p>
+<p>Check out the GCC sources by issuing the command:</p>
 
 <blockquote><p><code>
 git clone git+ssh://<i>username</i>@gcc.gnu.org/git/gcc.git gcc
@@ -99,7 +97,7 @@ git config --global user.email "<i>Your Email Address</i>"
 
 <p>If you wish to use a different name or email address for GCC
 commits from that in <samp>$HOME/.gitconfig</samp>, you can configure
-that in an individual Git tree using a similar command
+that in an individual Git tree using similar invocations
 without <code>--global</code>.</p>
 
 <hr />
@@ -241,16 +239,15 @@ automatically added to the corresponding ChangeLog files based
 on the git commit message.  See the documentation of
 <a href="codingconventions.html#ChangeLogs">ChangeLog format</a>.</li>
 
-<li>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.</li>
+<li>Make sure to rebuild any generated files affected by
+the patch and commit them with the files explicitly modified.</li>
 
 <li>If the patch adds any new files, such as testcases, use <code>git
 add</code> to make Git aware of them.</li>
 
 <li>We recommend using "<code>git diff HEAD</code>" 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.</li>
 
 <li>Use "<code>git commit</code>" to check in the patch; either name
@@ -317,7 +314,7 @@ other developers, you can use <code>git push</code> as follows:</p>
 git push origin $BRANCH:devel/$BRANCH
 </pre></blockquote>
 
-<p>Also, please document such branches at the
+<p>Please document such branches at the
 <a href="git.html#devbranches">list of development branches</a>.
 </p>
 
@@ -450,9 +447,8 @@ much the same way as C function names are used).</p>
 
 <h3>contrib/git-fetch-vendor.sh</h3>
 
-<p><em>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.</em></p>
+<p><em>Vendor spaces are controlled by the named vendor.  Do not push
+changes to that space without their express permission.</em></p>
 
 <p>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