vagrant/lib
Mitchell Hashimoto a677c15e86 Use `next` instead of `return` for 1.8.x compatibility.
Since we're not calling this lambda from inside a method, the `return`
causes a LocalJumpError on 1.8.x. It appears this functionality works
fine on 1.9.x but we'd like to support both. The correct behavior
appears to use `next`.
2012-06-23 10:47:01 -07:00
..
vagrant Convert the path to a string because it may be a Pathname 2012-06-22 21:06:49 -07:00
vagrant.rb Use `next` instead of `return` for 1.8.x compatibility. 2012-06-23 10:47:01 -07:00