From patchwork Tue Nov 30 12:22:45 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Nathan Sidwell X-Patchwork-Id: 48278 Return-Path: X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3821F385C40F for ; Tue, 30 Nov 2021 12:26:10 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) by sourceware.org (Postfix) with ESMTPS id 3C027385C409 for ; Tue, 30 Nov 2021 12:22:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3C027385C409 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=acm.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-qk1-x72c.google.com with SMTP id d2so26436572qki.12 for ; Tue, 30 Nov 2021 04:22:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:message-id:date:mime-version:user-agent:content-language:to :cc:from:subject; bh=xtmpTS6202Sm6waYCpFvb73KvhvYYQmErmMEiR1Nkew=; b=nYbK1yhdqqdk1g7YjyO3fjysHBC9MK9+R4xSssHl4y0Ypsx2Izhq/xzNYcmFjHuPZ/ wZrEt3gTKYNhxyKvg+7Ba456+DHtRTQgZy0iksHCL4Z5y/1NFmg/QXogb4XJOeSkSBKp dhp6+kGgsXsKRUu3ZAnc+dL1VFX2VHn3zIxx/obyVtZBVP4sz7ZJbuT/63kMKaMFMxlJ 4AsPgcKky7Yc0KRPn3wMjuBmgupzGrslKKwGDrXhGANZ7h8/D99j3hvqlywSkyhjccs3 CzhbF606NkO0odOkn/KMqugmguMRAlOcmPVdu3kOU6IkAdAuphRGIcgXz1neWdiGVIHl q8XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:message-id:date:mime-version:user-agent :content-language:to:cc:from:subject; bh=xtmpTS6202Sm6waYCpFvb73KvhvYYQmErmMEiR1Nkew=; b=WDg9jmEZ3iDP4SCB19oTCL+9jGC+yfGIHZy3yj4AhCeCiJwnOCy3mdzIrLGEzVxvZA uF6knhrvxrmW+FYnWzVns2hP43a/s1sMYxJFkRycHga1ZFankVrMzDVPNw4lHHTJbwqX i+/JXh+iY3OEXSdgUouXIDznYX0iMlliF9ovBZA8+Hrv+B0J8vIEbzT6pNGI+0p96njf cy5xr9i6yhUJOPFQIBFajWD+xKiTiD4Mg6x+Jj6Ohw83bVWrs86kzxsEcEdxljw8QhdR A4mcRcLQUmSxJGqdxMkTUFJrQS4CfFrSZPwWXAxQeGuYF4R4W5PiZyDjDo064JLNLPZV qbqA== X-Gm-Message-State: AOAM533UhI8RaSsCnwR3MX0W99XEASw+fn6mbmmIouZy7d92gfsDOh53 fk3SamnBLiIBUFl+wGr1qUg8vvKWHnw= X-Google-Smtp-Source: ABdhPJw9DGueGBt1xaa9piFfYciqcpJz8/YegY6a/qehCzStx1FuRqRhkuG6eLTY6gP/uuFr2MDsyQ== X-Received: by 2002:a05:620a:4152:: with SMTP id k18mr35784586qko.579.1638274966710; Tue, 30 Nov 2021 04:22:46 -0800 (PST) Received: from ?IPV6:2620:10d:c0a3:1407:29de:2e1e:229b:a71? ([2620:10d:c091:500::1:dedf]) by smtp.googlemail.com with ESMTPSA id f34sm10206203qtb.7.2021.11.30.04.22.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 Nov 2021 04:22:46 -0800 (PST) Message-ID: Date: Tue, 30 Nov 2021 07:22:45 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Content-Language: en-US To: Gerald Pfeifer From: Nathan Sidwell Subject: gender-agnostic pronouns X-Spam-Status: No, score=-3039.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_EF, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, GIT_PATCH_0, HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: GCC Patches Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Sender: "Gcc-patches" I've committed this change to use gneder agnostic pronouns on the non-historical web documents. and if you're upset that Those Are Plural!, assemble this URL and watch youtube /watch?v=46ehrFk-gLk&t=87s at about the 2 minute mark nathan From b5a0f250f0f05364a51c331d040d78bf15057884 Mon Sep 17 00:00:00 2001 From: Nathan Sidwell Date: Tue, 30 Nov 2021 07:12:44 -0500 Subject: [PATCH] Use gender-agnostic pronouns Use they/them/their in non-historical documents --- htdocs/bugs/management.html | 6 +++--- htdocs/contribute.html | 2 +- htdocs/develop.html | 2 +- htdocs/fortran/index.html | 4 ++-- htdocs/gitwrite.html | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/htdocs/bugs/management.html b/htdocs/bugs/management.html index 18fee991..97ef8299 100644 --- a/htdocs/bugs/management.html +++ b/htdocs/bugs/management.html @@ -203,7 +203,7 @@ fixing (the rationale is that a patch will have to go to the newest release branch before any other release branch). The priority of a regression should initially be set to P3. The milestone and the priority can -be changed by the release manager and his/her delegates.

+be changed by the release manager and their delegates.

If a patch fixing a PR has been submitted, a link to the message with the patch should be added to the PR, as well as the @@ -224,8 +224,8 @@ release versions) should get "minor" severity and the additional keyword

Bugs in component "bootstrap" that refer to older releases or snapshots/CVS versions should be put into state "WAITING", -asking the reporter whether she can still reproduce the problem and to -report her findings in any case (whether positive or negative).

+asking the reporter whether they can still reproduce the problem and to +report their findings in any case (whether positive or negative).

  • If the response is "works now", close the report,
  • diff --git a/htdocs/contribute.html b/htdocs/contribute.html index 423ce9de..c0223738 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -397,7 +397,7 @@ to point out lack of write access in your initial submission, too.

    Announcing Changes (to our Users)

    -

    Everything that requires a user to edit his Makefiles or his source code +

    Everything that requires a user to edit their Makefiles or source code is a good candidate for being mentioned in the release notes.

    Larger accomplishments, either as part of a specific project, or long diff --git a/htdocs/develop.html b/htdocs/develop.html index 4b1f9468..9880ad42 100644 --- a/htdocs/develop.html +++ b/htdocs/develop.html @@ -60,7 +60,7 @@ branch in the publicly accessible GCC development tree.)

There is no firm guideline for what constitutes a "major change" -and what does not. If a developer is unsure, he or she should ask for +and what does not. If a developer is unsure, they should ask for guidance on the GCC mailing lists. In general, a change that has the potential to be extremely destabilizing should be done on a branch.

diff --git a/htdocs/fortran/index.html b/htdocs/fortran/index.html index 1d140b3a..1984a297 100644 --- a/htdocs/fortran/index.html +++ b/htdocs/fortran/index.html @@ -117,11 +117,11 @@ changes.
  • Approval should be necessary for patches which don't fall under the obvious rule. So, with the approver list put in place, everybody (except maintainers) should still seek approval for -his/her patches. We have found the mutual peer review process really +their patches. We have found the mutual peer review process really works well.
  • Patches should only be reviewed by people who know the affected parts of the compiler. (i.e. the -reviewer has to be sure he/she knows stuff well enough to make a +reviewer has to be sure they know stuff well enough to make a good judgment.)
  • Large/complicated patches should still go by one of our maintainers, or team consensus.
  • diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 92740209..9de5de27 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -37,7 +37,7 @@ 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. +Include the name of your sponsor and CC: them. Otherwise use this form, again specifying your sponsor.

    -- 2.31.1