Use git rev-parse to obtain current branch name

Obtaining the current branch name using describe is roundabout and the
tokenization that includes '/' is broken for any branch with '/' in
its name (a common git practice). Using `git rev-parse --abbrev-ref
HEAD` seems to provide the current branch name in an easy to parse
fashion.
Merge pull request #22 from seth/sf/use-rev-parse

Use git rev-parse to obtain current branch name
Remove unused imports from merl_lib in edown_xmerl
Fix "close" of markdown headers, octothorpe counts should match
Handle explicit code blocks separately from edoc generated blocks

Explicit code blocks (e.g. ```CODE''' in edoc) use an intermediate
'pre' tag and are now rendered using Github Flavored Markdown "fenced"
code block style. Using the markdown code block as opposed to 'pre'
tags avoids needing to escape content in the block and slightly
improves the readability of the generated markdown.

The edoc generated function and type spec descriptions use a 'pre_pre'
tag. The code now assumes that the pre_pre elements contain code with
anchor tags for linking, but no other HTML tags. Special processing is
added to wrap the 'pre_pre' blocks in '<pre><code>' tags and to
translate angle brackets in the body of such tags to the appropriate
HTML entity (&gt;, &lt;).

This patch also adjusts newline behavior for generated markdown.
Paragraphs now begin/end with a single \n. As a result, the formatting
of ol and ul lists in markdown is improved.
Detect if package support has been removed
Merge branch 'master' of github.com:esl/edown
add rebar customization scripts; github URL rewrites
Added priv/scripts/rebar.config.script
Merge branch 'sf/markdown-tweaks' of github.com:seth/edown
regenerated docs after seth's patches
Experimental: Add option to name branch for top_level_README

See https://github.com/esl/edown/issues/8

If {top_level_readme, {Path, URL, Branch}} is specified, edown will
use Branch instead of deriving the current branch when linking to
the top-level README file.