Removed github-markdown dependency from gollum-lib.gemspec
added 'github-markdown' development dependency to make tests pass
Simplified #ref_to_sha! implementation to remove empty rescue clause.
Merge pull request #43 from repotag/master

Simplified #ref_to_sha! implementation to remove empty rescue clause.
Allow binary files to be uploaded
Merge pull request #45 from singlebrook/binary_upload_fix

Allow binary files to be uploaded
Merge pull request #42 from 1gor/patch-1

Remove github-markdown dependency from gollum-lib.gemspec
Refactoring of #get_disk_reference to fix symlink issue on JRuby.
Merge pull request #46 from repotag/realpath_fix

Refactoring of #get_disk_reference to fix symlink issue on JRuby.
Use gitlab fork of grit for Ruby 2.0 support

http://rubygems.org/gems/gitlab-grit

Fix charlock_holmes install error

Test on Ruby 2.0.0
Merge pull request #47 from bootstraponline/master

Use gitlab fork of grit for Ruby 2.0 support
Release 1.0.7
Update gemspec
Merge pull request #48 from bootstraponline/master

Update gemspec
Release 1.0.8
Constrain gitlab-grit to 2.6.0. Fixes gollum/gollum#757
Release 1.0.9
gollum-lib changes required to implement per-page uploads
Merge pull request #49 from anchor/per-page-uploads

gollum-lib changes required to implement per-page uploads
Convert the markup class to use "filter chains"

Refactor out the steps required to turn a marked-up file into a HTML
fragment ready for display into individual classes.  The benefit of this is
that users can modify the processing chain for their own needs, without
needing to go subclassing Gollup::Markup.  This should be a big win.

It's a conceptually simple change that gets a bit messy, since the
extraction and processing code got its tentacles into a few places.

In essence, each phase of rendering a page is encapsulated in a separate
class with extract/process methods, more-or-less mirroring the existing
structure.  I had to take a bit of a gamble between sharing state between
filter steps (via the markup class instance) and redoing some things
multiple times (HTML parsing/assembly), but I felt that was cleaner than the
alternatives, especially since if we store a parsed document, we'd have to
make sure that cache wasn't invalidated by an intermediate step.