Remove special case formatting for vnode_gets.
BZ1020: Add ETag and Last-Modified headers to responses containing siblings.
BZ1020: Add conditional headers for PUT/POST with returnbody=true.
Correct reference to riak_core_vnode_master to riak_core_vnode_manager
Merge pull request #278 from basho/az1089_kv_status

Correct reference to riak_core_vnode_master to riak_core_vnode_manager
Log post-commit errors

If a post-commit fails but there is no evidence in the logs did it actually
fail?  I dunno, but we should log post-commit failures.
Add mod/fun information for all failure cases
Use counters for pre/post commit hook failures
Make pre/post commit hook decoding consistent
Still need try/catch incase Result is not an object
Update EQC test for slightly new return from invoke_hook
Added fail and {fail, Reason} postcommit hooks to put_fsm_eqc.
Made put_fsm_eqc set the lager debug log level.
Merge branch 'az1046-postcommit-error-counter-master'
Fix eunit timeout for eleveldb EQC test
Merge pull request #280 from basho/adt-fix-eunit-timeout

Fix eunit timeout for eleveldb EQC test
Fix starting riak_core now lager is a dep and make buildbot happy

The put_fsm_eqc test was including headers in a way that assumed riak_kv
was checked out to a directory called 'riak_kv', which isn't the case
whem buildbot runs a per-repo eunit run. This patch fixes the includes
to always work regardless of the checkout directory.
Merge pull request #281 from basho/az1095-fix-broken-tests

Fix starting riak_core now lager is a dep and make buildbot happy
Set `small_vclock` equal to `big_vclock`

The default value of `small_vclock` has been changed to be equal to
`big_vclock` in order to delay or even prevent unnecessary sibling
creation in a Riak deployment with bidirectional cluster replication.
When you replicate a pruned vector clock the other cluster will think
it isn't a descendent, even though it is, and create a sibling.  By
raising `small_vclock` to match `big_vclock` we reduce the frequency
of pruning and thus siblings.  Combined with vnode vclocks, sibling
creation, for this particular reason, may be entirely avoided since
the number of entries will almost always stay below the threshold in a
well behaved cluster (i.e. one not under constant node membership
change or network partitions).

See also: https://issues.basho.com/show_bug.cgi?id=1310

Note that this is not a fix for the above issue, just an attempt to
reduce it's likelihood.
Merge branch 'az1078-small_vclock-default'