Initialize `@content_type` per request not per connection
Add a test of Content-Type initialization in in_http
Fix test for ruby 2.0.0
Merge pull request #400 from komamitsu/in_http_content_type

in_http: Initialize @content_type per request not per connection
add use-v0-config option
Merge pull request #431 from fluent/use-v0-config

add use-v0-config option
add single quoted literal
Merge pull request #437 from fluent/single_quote_string

add single quoted string literal
add config_parser_spec for single quoted string
Merge pull request #438 from fluent/single_quote_stirng_config_parser

add config_parser_spec for single quoted string
Update travis.yml for v0.10 branch
Get coverage to work

Measure lib/* coverage based on test execution in addition to spec.
Test and spec changes are for satisfying generic rules below.

 * simplecov requires target code to be loaded before invoking
   SimpleCov.start.
 * Invoke SimpleCov.start once. Multiple call works if use_merging =
   true (default) but unnecessarily complex.

Report from 'rake coverage' at this point.

  All Files (69.33% covered at 842.16 hits/line)
  64 files in total. 5931 relevant lines. 4112 lines covered and 1819 lines missed
Add explicit test/unit dependency

This change needs consultation with CRuby guys.

 * CRuby trunk and 2.2.0-preview1 needs this but is this intentional
   change?
 * If this change only needs for developers living with CRuby trunk?

FWIW I once heard that this is only needed by the ruby command built
from svn repo but unnecesarry in general ruby installation.
Merge pull request #441 from nahi/topic_get_coverage_to_work

Get coverage to work
Merge pull request #442 from nahi/topic_explicit_test_unit_dependency

[WIP] Add explicit test/unit dependency
Remove zfile buffer
Merge pull request #445 from fluent/remove-buf-zfile

Remove zfile buffer
add literal_example.conf
Merge pull request #443 from fluent/single_quote_string_literal_example

add literal_example.conf
'--suppress-repeated-stacktrace' is true by default

We keep this option for backward compatibility.
Maybe, there is no user who wants to disable this option.
We will remove related code in the future.