summaryrefslogtreecommitdiff
path: root/lib/rubygems/version.rb
diff options
context:
space:
mode:
authorzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2014-01-20 04:57:31 +0000
committerzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2014-01-20 04:57:31 +0000
commitdff0aa5a536937db2606b870aad42c2caee60adb (patch)
tree8fdd94b9da6190f47d2ab75f1e191ca1a37bb7a5 /lib/rubygems/version.rb
parent5ecbe189af77c309845d662f26c0b2797bde2915 (diff)
* lib/rubygems/version.rb: [DOC] Use gender-neutral pronouns [ci skip]
* lib/rubygems/security.rb: ditto git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44661 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'lib/rubygems/version.rb')
-rw-r--r--lib/rubygems/version.rb21
1 files changed, 10 insertions, 11 deletions
diff --git a/lib/rubygems/version.rb b/lib/rubygems/version.rb
index fda8b0b5d4..63a74b75d8 100644
--- a/lib/rubygems/version.rb
+++ b/lib/rubygems/version.rb
@@ -81,8 +81,8 @@
#
# * Any "public" release of a gem should have a different version. Normally
# that means incrementing the build number. This means a developer can
-# generate builds all day long for himself, but as soon as he/she makes a
-# public release, the version must be updated.
+# generate builds all day long, but as soon as they make a public release,
+# the version must be updated.
#
# === Examples
#
@@ -99,26 +99,25 @@
# Version 1.1.1:: Fixed a bug in the linked list implementation.
# Version 1.1.2:: Fixed a bug introduced in the last fix.
#
-# Client A needs a stack with basic push/pop capability. He writes to the
-# original interface (no <tt>top</tt>), so his version constraint looks
-# like:
+# Client A needs a stack with basic push/pop capability. They write to the
+# original interface (no <tt>top</tt>), so their version constraint looks like:
#
# gem 'stack', '~> 0.0'
#
# Essentially, any version is OK with Client A. An incompatible change to
-# the library will cause him grief, but he is willing to take the chance (we
-# call Client A optimistic).
+# the library will cause them grief, but they are willing to take the chance
+# (we call Client A optimistic).
#
-# Client B is just like Client A except for two things: (1) He uses the
-# <tt>depth</tt> method and (2) he is worried about future
-# incompatibilities, so he writes his version constraint like this:
+# Client B is just like Client A except for two things: (1) They use the
+# <tt>depth</tt> method and (2) they are worried about future
+# incompatibilities, so they write their version constraint like this:
#
# gem 'stack', '~> 0.1'
#
# The <tt>depth</tt> method was introduced in version 0.1.0, so that version
# or anything later is fine, as long as the version stays below version 1.0
# where incompatibilities are introduced. We call Client B pessimistic
-# because he is worried about incompatible future changes (it is OK to be
+# because they are worried about incompatible future changes (it is OK to be
# pessimistic!).
#
# == Preventing Version Catastrophe: