Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] btrfs-progs: Doc: Add warning and note on btrfs-convert.
Date: Fri, 3 Apr 2015 09:56:48 +0000 (UTC)	[thread overview]
Message-ID: <pan$d3473$5acd4d32$9b1eb3cc$28bf977f@cox.net> (raw)
In-Reply-To: 20150403121656.35782bda@natsu

Roman Mamedov posted on Fri, 03 Apr 2015 12:16:56 +0500 as excerpted:

> On Fri, 3 Apr 2015 15:06:46 +0800 Qu Wenruo <quwenruo@cn.fujitsu.com>
> wrote:
> 
>> >> +WARNING: If one hopes to rollback to ext2/3/4, he or she should not
>> >> execute
> 
> It also seems a bit awkward to spell out "he or she", if you want to
> refer to a user without specifying the gender, in software documentation
> it's more common to use "they":
> https://en.wikipedia.org/wiki/Singular_they

Tho as the link notes, "singular they" has been and remains somewhat 
controversial.

While "singular they" is accepted as correct (and as the link points out, 
has been used by certain professional writers in some instances for 
centuries, so it's not new!), so is "he or she", with both being 
generally agreed to be slightly awkward attempts at political 
correctness, for those uncomfortable with the arguably more traditional 
masculine second-person-generic when referring to a human, feminine when 
personifying an animal or inanimate object.

An individual's choice of usage will depend on how politically correct 
and inclusive their (usage in point) intent is, vs how traditional they 
intend to be.

So either usage would have been fine here in a modern context, as would  
the more traditional "he" in a traditional context, since the individual 
is assumed to be a person not an object.

The ones that really bother me, however, are the ones that arguably 
inappropriately use a feminine second-person singular when obviously 
referring to a (gender-unknown) person, not an object.  That's in-your-
face political correctness to the point of extremism, partly because it 
triggers a reparse, since the reader is then left to figure out whether 
the intent was really specifically human female or an inanimate object, 
where they had thought human generic or male, previously, and when the 
traditional usage doesn't match, the extreme in-your-face politically 
correct assertiveness of the deliberate female choice over singular-they, 
appropriate he/she form, or traditional gender-unknown but assumed human 
masculine, is jarring, to say the least.  I understand why some people 
make that choice and respect that they have the right to choose it, but 
still resent that they don't have at least minimal respect for my need as 
a reader to read without jarringly forced reparse.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-04-03  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  1:21 [PATCH v3] btrfs-progs: Doc: Add warning and note on btrfs-convert Qu Wenruo
2015-04-03  5:55 ` Duncan
2015-04-03  7:06   ` Qu Wenruo
2015-04-03  7:16     ` Roman Mamedov
2015-04-03  9:56       ` Duncan [this message]
2015-04-03  8:33     ` Duncan
2015-04-07 15:04     ` David Sterba

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='pan$d3473$5acd4d32$9b1eb3cc$28bf977f@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@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