From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124475 invoked by alias); 17 Jan 2020 21:17:54 -0000 Mailing-List: contact gcc-cvs-wwwdocs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-cvs-wwwdocs-owner@gcc.gnu.org Received: (qmail 124428 invoked by uid 9022); 17 Jan 2020 21:17:54 -0000 Date: Fri, 17 Jan 2020 21:17:00 -0000 Message-ID: <20200117211754.124425.qmail@sourceware.org> From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 144607e8df2b31f6b4e5787804fb587d08935341 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: c0eb9de3940874588c718198697825646374bf18 X-Git-Newrev: 144607e8df2b31f6b4e5787804fb587d08935341 X-SW-Source: 2020/txt/msg00042.txt 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 144607e8df2b31f6b4e5787804fb587d08935341 (commit) from c0eb9de3940874588c718198697825646374bf18 (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 144607e8df2b31f6b4e5787804fb587d08935341 Author: Gerald Pfeifer Date: Fri Jan 17 22:09:42 2020 +0100 Simplify and adjust to the switch from SVN to Git. Remove a section that only applies to SVN and some specifics on encoding patches in mails that are rarely relevant. Shorten the initial statement, the note on copyright disclaimers, and trim some further overly picky/explicit statements. Use active voice and improve markup in one case each. diff --git a/htdocs/contribute.html b/htdocs/contribute.html index ae19cb88..042ff069 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -1,5 +1,6 @@ + @@ -12,12 +13,11 @@

Contributing to GCC

We strongly encourage individuals as well as organizations to -contribute to the development of GCC in the form of new features, new +

We strongly encourage contributions in the form of features, new or improved optimizations, bug fixes, documentation updates, web page improvements, etc....

There are certain legal requirements and style issues which all +

There are certain legal requirements and style issues which contributions must meet:

If a contributor is reluctant to sign a copyright assignment for a change, a copyright disclaimer to put the change in the public domain is -acceptable as well. The copyright disclaimer form is different than an -employer disclaimer form. A copyright assignment is more convenient if a +acceptable as well. A copyright assignment is more convenient if a contributor plans to make several separate contributions.

Small changes can be accepted without a copyright disclaimer or a +

We can accept small changes without a copyright disclaimer or a copyright assignment on file.

Much of GCC's code is used only by some targets, or used in quite different ways by different targets. When choosing targets to test a patch with, make sure that your selections exercise all aspects of the -code you are changing. For instance, a change to conditional branch -handling should be tested both with targets that use cc0, -and targets that don't.

You will of course have tested that your change does what you expected it to do: fix a bug, improve an optimization, add a new @@ -127,9 +124,8 @@ must perform a complete bootstrap; however, running other language testsuites is not necessary.

In all cases you must test exactly the change that you intend to -submit; it's not good enough to test an earlier variant. The tree -where you perform this test should not have any other changes applied -to it. Include all your new testcases in your testsuite run.

Documentation Changes

The patch itself

-If you are accessing the SVN repository at -gcc.gnu.org, please configure your svn to use GNU diff -and generate patches using the "-up" or -"-cp" options. -See SVN setup instructions -for more details.
Do not include generated files as part of the patch, just mention -them in the ChangeLog (e.g., "* configure: Regenerate."). +them in the ChangeLog (e.g., "* configure: Regenerate.").

We prefer patches posted as plain text or as MIME parts of type -text/x-patch or text/plain, disposition -inline, encoded as 7bit or -8bit. +text/x-patch or text/plain. It is strongly discouraged to post patches as MIME parts of type application/whatever, disposition attachment or encoded as base64 or -quoted-printable. Avoid MIME large-message splitting -(message/partial) at all costs.

quoted-printable

If the patch is too big or too mechanical, posting it gzipped or bzip2ed and uuencoded or encoded as a base64 MIME part is ----------------------------------------------------------------------- Summary of changes: htdocs/contribute.html | 35 +++++++++++------------------------ 1 file changed, 11 insertions(+), 24 deletions(-) hooks/post-receive -- gcc-wwwdocs