aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/result.rb
diff options
context:
space:
mode:
authorclaudiob <claudiob@gmail.com>2015-05-12 14:51:19 -0700
committerclaudiob <claudiob@gmail.com>2015-05-12 14:51:19 -0700
commit0080a886b2297592a95c1286eadff54a1e33fb86 (patch)
treea527756011d5eeec597c9e078646f50bc91f8ea5 /activerecord/lib/active_record/result.rb
parente99d909928e4b919ace290c3ace3fbaceeba70da (diff)
downloadrails-0080a886b2297592a95c1286eadff54a1e33fb86.tar.gz
rails-0080a886b2297592a95c1286eadff54a1e33fb86.tar.bz2
rails-0080a886b2297592a95c1286eadff54a1e33fb86.zip
[ci skip] Don’t encourage `sudo gem install`
I think we are better off leaving `sudo` outside of the documented way of installing gems (`activerecord`, `actionpack`, …). We don’t want newbies to think that `sudo` is required or, even worse, than they actually have to type `[sudo] gem install`. In most scenarios, `sudo` is not needed to install gems, and people who do need it, probably already know about it. What do you think? :grin:
Diffstat (limited to 'activerecord/lib/active_record/result.rb')
0 files changed, 0 insertions, 0 deletions