git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	git@vger.kernel.org, Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH 0/2] Avoid gender pronouns
Date: Mon, 14 Jun 2021 10:27:50 +0900	[thread overview]
Message-ID: <xmqq5yyh1bhl.fsf@gitster.g> (raw)
In-Reply-To: <87k0my1bgp.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sun, 13 Jun 2021 09:15:01 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Fri, Jun 11 2021, Felipe Contreras wrote:
>
>> The latest solution looking for a problem [1] is to use the actively
>> debated among linguists singular "they" [2].
>>
>> Leaving aside the linguistic intricacies that not all singular "they" are
>> equal [3], and the overwhelming sentiment that these kinds of political
>> discussions don't provide value for this community [4], the "issue" can
>> be easily solved by simply using different wording.
>>
>>   - The reviewer herself
>>   + The reviewers themselves
>>
>> Problem solved.
>>
>> Cheers.
>>
>> [1] https://lore.kernel.org/git/pull.975.git.1623085069.gitgitgadget@gmail.com/
>> [2] https://www.theatlantic.com/culture/archive/2013/01/singular-their-affront-good-writing/319329/
>> [3] https://ahdictionary.tumblr.com/post/147597257733/updated-usage-note-they
>> [4] https://lore.kernel.org/git/87wnrooa17.fsf@evledraar.gmail.com/
>>
>> Felipe Contreras (2):
>>   doc: avoid using the gender of other people
>>   comments: avoid using the gender of our users
>
> This looks good to me, especially the reduction in verbosity in hunks
> like:
> 	
> 	- * parameters to the callback, `strbuf_expand()` passes a context pointer,
> 	- * which can be used by the programmer of the callback as she sees fit.
> 	+ * parameters to the callback, `strbuf_expand()` passes a context
> 	+ * pointer with any kind of data.
>
> The comment gives you the same information, but now it takes a shorter
> time to read it.

Looks good to me.  I am tempted to suggest that we should take this
as "fix to the documentation proper".  We can discuss the policy and
guideline separately.

      reply	other threads:[~2021-06-14  1:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 20:28 [PATCH 0/2] Avoid gender pronouns Felipe Contreras
2021-06-11 20:28 ` [PATCH 1/2] doc: avoid using the gender of other people Felipe Contreras
2021-06-15 13:28   ` Derrick Stolee
2021-06-15 16:30     ` Felipe Contreras
2021-06-11 20:28 ` [PATCH 2/2] comments: avoid using the gender of our users Felipe Contreras
2021-06-15 13:31   ` Derrick Stolee
2021-06-15 14:16     ` Paul Smith
2021-06-15 16:39       ` Felipe Contreras
2021-06-15 16:36     ` Felipe Contreras
2021-06-12  1:17 ` [PATCH 0/2] Avoid gender pronouns Bagas Sanjaya
2021-06-12  1:39   ` Felipe Contreras
2021-06-12 23:24 ` Robert Karszniewicz
2021-06-13  7:15 ` Ævar Arnfjörð Bjarmason
2021-06-14  1:27   ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq5yyh1bhl.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=dstolee@microsoft.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).