Handle coercion correctly when MergeInitializer is used
Let coerce_key support an array of keys to coerce. Also add an alias to the method `coerce_keys`
initialize translations before other properties in trash
enhance Hashie::Extensions::MethodReader#respond_to?, Hashie::Extensions::MethodWriter#respond_to? and Hashie::Extensions::MethodQuery#respond_to?   so that it supports the optional include_private argument - needed to work properly with some other modules like ActiveModel::Validations
fix typo from previous commit
defined Hashie::Mash#fetch
accept x86-mingw32 platform in Gemfile
spec code formatting
remove unnecessary scoping
fix typo
add license information to gemspec

This way you can get this info from rubygems.org API
Merge pull request #72 from jordimassaguerpla/master

add license information to the gemspec
Merge pull request #71 from jcamenisch/patch-1

fix typo
Merge pull request #27 from mattfawcett/master

Coercion does not work with MergeInitializer
Merge pull request #28 from mattfawcett/multiple_coercion

Let coerce_key support an array of keys to coerce.
Merge pull request #39 from sleverbor/initialize_translations_first

initialize translations before other properties in trash
fix spacing, add comment to Trash#initialize_attributes
Merge pull request #66 from arthwood/master

Fix 'Use of fetch() method with Mash'
clean up Mash#fetch spec formatting
Merge pull request #62 from dlupu/master

enhance respond_to? method