summaryrefslogtreecommitdiff
path: root/lib/rubygems/version.rb
diff options
context:
space:
mode:
authorhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-12-11 02:53:09 +0000
committerhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-12-11 02:53:09 +0000
commit0c5841bead6e7910ec27e2705849b100ace143e2 (patch)
treef00716fa1974a4efdc03845b8960800ed6b673e4 /lib/rubygems/version.rb
parent165e10b6cf73f723c2f6af676b70aeb2d8cf85c9 (diff)
* lib/rubygems: Update to RubyGems 2.5.1
* test/rubygems: ditto. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@53032 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'lib/rubygems/version.rb')
-rw-r--r--lib/rubygems/version.rb2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/rubygems/version.rb b/lib/rubygems/version.rb
index e2ee59a0c2..16e20c5246 100644
--- a/lib/rubygems/version.rb
+++ b/lib/rubygems/version.rb
@@ -107,7 +107,7 @@
# 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'
+# gem 'stack', '>= 0.0'
#
# Essentially, any version is OK with Client A. An incompatible change to
# the library will cause them grief, but they are willing to take the chance