threads / patch / 38001

patchdate.c: phrase a comment gender neutral

Subject: [PATCH] date.c: phrase a comment gender neutral

## tl;dr

4 messages between Nov 18, 2014 and Nov 18, 2014. Diffs are folded; open one to read it.

replies: 3people: 3as markdown or json

Stefan Beller· Nov 18, 2014, 19:24 UTC · lore

When looking for suitable functions to print dates, I found this gem. Let's make it gender neutral as nowadays people get upset by this gender debate.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 date.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Show changes to date.c +1 −1

diff --git a/date.c b/date.c
index 59dfe57..19fb439 100644
--- a/date.c
+++ b/date.c
@@ -732,7 +732,7 @@ int parse_expiry_date(const char *date, unsigned long *timestamp)
 		/*
 		 * We take over "now" here, which usually translates
 		 * to the current timestamp.  This is because the user
-		 * really means to expire everything she has done in
+		 * really means to expire everything they have done in
 		 * the past, and by definition reflogs are the record
 		 * of the past, and there is nothing from the future
 		 * to be kept.

-- 
2.2.0.rc2.5.gf7b9fb2

Jonathan Nieder· Nov 18, 2014, 19:42 UTC · re: Stefan Beller · lore

Re: [PATCH] date.c: phrase a comment gender neutral

Stefan Beller wrote:

> When looking for suitable functions to print dates,
> I found this gem. Let's make it gender neutral as
> nowadays people get upset by this gender debate.

Eh, I'm not upset.

Hope that helps, Jonathan

Junio C Hamano· Nov 18, 2014, 20:03 UTC · re: Stefan Beller · lore

Re: [PATCH] date.c: phrase a comment gender neutral

Stefan Beller <sbeller@google.com> writes:

> When looking for suitable functions to print dates,
> I found this gem. Let's make it gender neutral as
> nowadays people get upset by this gender debate.

For some time I used to use "she/her" on Mondays, Wednesdays and Fridays and "he/his" on other days to balance them, and you are seeing the artifact of that.

Some people might feel that we would be better off using "they" all the time, but IMO it's such a minor thing that once it _is_ in the tree, it's not really worth the patch noise to go and fix it up.

Show 19 quoted lines

>
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
>  date.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/date.c b/date.c
> index 59dfe57..19fb439 100644
> --- a/date.c
> +++ b/date.c
> @@ -732,7 +732,7 @@ int parse_expiry_date(const char *date, unsigned long *timestamp)
>  		/*
>  		 * We take over "now" here, which usually translates
>  		 * to the current timestamp.  This is because the user
> -		 * really means to expire everything she has done in
> +		 * really means to expire everything they have done in
>  		 * the past, and by definition reflogs are the record
>  		 * of the past, and there is nothing from the future
>  		 * to be kept.

Stefan Beller· Nov 18, 2014, 20:07 UTC · re: Junio C Hamano · lore

Re: [PATCH] date.c: phrase a comment gender neutral

ok.

I'll stop sending such gender related nits.

On Tue, Nov 18, 2014 at 12:03 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 35 quoted lines

> Stefan Beller <sbeller@google.com> writes:
>
>> When looking for suitable functions to print dates,
>> I found this gem. Let's make it gender neutral as
>> nowadays people get upset by this gender debate.
>
> For some time I used to use "she/her" on Mondays, Wednesdays and
> Fridays and "he/his" on other days to balance them, and you are
> seeing the artifact of that.
>
> Some people might feel that we would be better off using "they" all
> the time, but IMO it's such a minor thing that once it _is_ in the
> tree, it's not really worth the patch noise to go and fix it up.
>
>
>>
>> Signed-off-by: Stefan Beller <sbeller@google.com>
>> ---
>>  date.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/date.c b/date.c
>> index 59dfe57..19fb439 100644
>> --- a/date.c
>> +++ b/date.c
>> @@ -732,7 +732,7 @@ int parse_expiry_date(const char *date, unsigned long *timestamp)
>>               /*
>>                * We take over "now" here, which usually translates
>>                * to the current timestamp.  This is because the user
>> -              * really means to expire everything she has done in
>> +              * really means to expire everything they have done in
>>                * the past, and by definition reflogs are the record
>>                * of the past, and there is nothing from the future
>>                * to be kept.
>