summaryrefslogtreecommitdiff
path: root/lib/rubygems/commands/yank_command.rb
diff options
context:
space:
mode:
authorhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-01-09 14:20:10 +0000
committerhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2015-01-09 14:20:10 +0000
commit07b87cd239db5b556a6a9bb38ea78cd2540e4682 (patch)
tree6ee91107d81d30c7c9786dbf8f48be468827f851 /lib/rubygems/commands/yank_command.rb
parent30253e6a247425a6916132a79efed30db7eb2e2c (diff)
* lib/rubygems: Update to RubyGems HEAD(e53c54a).
* test/rubygems: ditto. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@49195 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'lib/rubygems/commands/yank_command.rb')
-rw-r--r--lib/rubygems/commands/yank_command.rb2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/rubygems/commands/yank_command.rb b/lib/rubygems/commands/yank_command.rb
index 3c7859e763..c05ee66283 100644
--- a/lib/rubygems/commands/yank_command.rb
+++ b/lib/rubygems/commands/yank_command.rb
@@ -21,7 +21,7 @@ via the webhooks. If you accidentally pushed passwords or other sensitive
data you will need to change them immediately and yank your gem.
If you are yanking a gem due to intellectual property reasons contact
-http://help.rubygems.org for permanant removal. Be sure to mention this
+http://help.rubygems.org for permanent removal. Be sure to mention this
as the reason for the removal request.
EOF
end