Permalink
Browse files

Remove references to thor in the README.

  • Loading branch information...
1 parent 7fbc799 commit bab6099763ba11a6550083e2ae90e44a1f7a5b02 @soveran soveran committed Apr 28, 2010
Showing with 4 additions and 4 deletions.
  1. +4 −4 README.markdown
View
@@ -9,23 +9,23 @@ Usage
Joe assumes you have a .gemspec file in the current directory and it will use it to build the gem. Once you have it, try this:
- $ thor joe:build
+ $ joe build
Congratulations, you should have your gem built inside the `pkg` directory.
Now go ahead and release your new gem to RubyGems.org:
- $ thor joe:release
+ $ joe release
Easy, right? Wait a few minutes until RubyGems.org updates its gems index and you will be able to run `sudo gem install foo`.
Maintaining a gemspec file
--------------------------
-The easiest way we've found to maintain a gemspec file is by creating a `foo.gemspec.erb` template ([see example](http://github.com/soveran/ohm/blob/e3ff3fb20c1337cb2c4de244e09ce9fa04ef397d/ohm.gemspec.erb)). Then you can use a Thor task to produce the real gemspec file:
+The easiest way we've found to maintain a gemspec file is by creating a `foo.gemspec.erb` template ([see example](http://github.com/soveran/ohm/blob/e3ff3fb20c1337cb2c4de244e09ce9fa04ef397d/ohm.gemspec.erb)). Then you can use Joe to produce the real gemspec file:
- $ thor joe:gemspec
+ $ joe gemspec
Installation

0 comments on commit bab6099

Please sign in to comment.