Update raft submodule and start using the new raft.Storage interface.
Merge pull request #190 from bdarnell/multiraft-storage

Update raft submodule and start using the new raft.Storage interface.
Fix race in multiraft test by calling Advance at the correct time.
Add detailed raft logging at V(5).
Update raft submodule
Google renamed download directory for releases.

The releases now have a 'v' as part of the version number for the
directory name.
Merge pull request #199 from jamesgraves/protobuf_download_moved

Download directory name for protobuf releases.
ignore ssl cert for curl in bootstrap

fixes #182
add install via "go get -d"
no-op change to un-confuse race detector (unless the race is real)

maybe fixes #201
Merge pull request #202 from tschottdorf/vndr

minor fixes
Restore cert validation in bootstrap.sh
Merge pull request #203 from bdarnell/bootstrap-validate-certs

Restore cert validation in bootstrap.sh
Merge pull request #195 from bdarnell/race-fix

Fix race in multiraft test by calling Advance at the correct time.
Add InternalMerge Command

Add the InternalMerge command, which is replacing the anticipated (but never
implemented) AccumulateTS command.  InternalMerge is similar to a put in that it
writes a single value to a key - however, the supplied value is *merged* into
the existing value instead of replacing it.

Merging is not transactional, and thus it is only exposed internally for usage
in certain operations which require a high write performance (such as the
accumulation of time series data).
Merge pull request #196 from cockroachdb/mtracy/internal_merge

Add InternalMerge Command
Introduce iterator to Engine interface, reimplement MVCCScan.

Added a vanilla iterator interface to engine for greater flexibility.
We now use the iterator for implementation of Engine.Iterate on both
RocksDB and Batch.

MVCCScan now uses a single iterator and invokes Iterator::Seek instead
of creating a new iterator at every step. This seems to speed up the
scan when benchmarked by roughly a factor of 2x. Benchmark timings are
here: https://docs.google.com/spreadsheets/d/1g8WTySNHLOQr-l0WDlbzkr-2h9dZj2bVrsW7yyJtw3Y/edit?usp=sharing

In the process of writing 100s of MB of data, discovered problems when
calling into go from C++ using an unsafe pointer of an object which
shouldn't have been GC'd. After poking around at it for a while and
not finding the problem, I decided to change the implementation so
that we no longer pass in a pointer to our Go struct. This appears to
have fixed the problems.
fix data races with in-mem iterator
Add two benchmarks
Response to Tobias' comments