Propose unified rev-parse API
Implement unified git_revparse
Deprecate git_revparse_single and _rangelike
Add rev-list example to makefiles
Reintroduce git_revparse_single.
Redeploy git_revparse_single.
Change git_revparse to output git_object pointers

This will probably prevent many lookup/free
operations in calling code.
Clean up example code.
Clean up minor details
Merge remote-tracking branch 'ben/unified-revparse' into development
Allow git_remote_ls after disconnecting from the remote

Keep the data around until free, as expected by our own fetch example
Is this crazy?
git_revision -> git_revspec
Update docs
remote: don't try to update FETCH_HEAD if no extra heads exist

Don't try to update anything if there are no heads to update. This
saves us from trying to look into a fetch refspec when there is none.

A better fix for compatibility with git when using remotes without
refspecs is still needed, but this stops us from segfaulting.
Fix examples
Merge pull request #1470 from carlosmn/remote-ls-after-close

Fetch fixes
Merge pull request #1469 from libgit2/vmg/unified-revision

Unified rev-parse, with a revision object
libgit2 0.18.0 "Big Ben"

This is the last minor release before 1.0preview1.

Highlights of this release include:

- Branch API
- Checkout head, index and tree
- Finished clone support
- Abstracted reference API to use custom backends
- Full diff support
- New (faster) packbuilder
- Push support
- New Remotes API
- Revparse support (single and range commits)
- Stash support
- Submodules support

As always, the full changelog is available at:

	http://libgit2.github.com/libgit2/#p/changelog

Yeah, it's a huge release. Releasing stuff sucks.
Expect 1.0 and API freeze in less than a month.

Your faithful maintainer,
	 vmg

Signed-off-by: Vicent Marti <tanoku@gmail.com>