hassox / warden_strategies

Description:	A collection of strategies for Warden edit
Homepage:	edit
Public Clone URL:	git://github.com/hassox/warden_strategies.git Give this clone URL to anyone. `git clone git://github.com/hassox/warden_strategies.git`
Your Clone URL:	git@github.com:hassox/warden_strategies.git Use this clone URL yourself. `git clone git@github.com:hassox/warden_strategies.git`

Updates the README

hassox (author)

Sat Oct 24 06:58:07 -0700 2009

warden_strategies /

name	age	history message
.document	Tue Sep 22 17:31:03 -0700 2009	Initial commit to warden_strategies. [hassox]
.gitignore	Tue Sep 22 17:31:03 -0700 2009	Initial commit to warden_strategies. [hassox]
LICENSE	Tue Sep 22 17:31:03 -0700 2009	Initial commit to warden_strategies. [hassox]
README.rdoc	Sat Oct 24 06:58:07 -0700 2009	Updates the README [hassox]
Rakefile	Sat Oct 24 06:53:47 -0700 2009	Updates the gem summary [hassox]
lib/	Sat Oct 24 06:51:19 -0700 2009	Adds a bcrypt strategy [hassox]
spec/	Sat Oct 24 05:37:49 -0700 2009	Adds a simple strategy [hassox]

README.rdoc

warden_strategies

A collection of warden strategies.

Note on Patches/Pull Requests

Fork the project.
Make your feature addition or bug fix.
Add tests for it. This is important so I don’t break it in a future version unintentionally.
Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but
```
 bump version in a commit by itself I can ignore when I pull)
```
Send me a pull request. Bonus points for topic branches.