NOP gofmt logstash-forwarder.go
MOD WIP various longstanding TODOs

ADD  cleanuped options
ADD  verbose flag
MOD  assert required options on startup
ADD  debug flag -- not yet hooked in
ADD  emit() to log - switched on verbose flag
NOP  cleanup emits from harvest on harvest start
DONE check harvest file is a regular file
DONE check stat errors on harvest init
NOP  gofmt affted files - TODO rest

TEST ADHOC OK
MOD new options and various cleanups

ADD  harvester reader buffer size option
MOD  remove all log imports - use emit throughout
MOD  use fault() inst of log.Fatalf to be consistent
MOD  WIP beefup error handling in config and registrar
NOTE see REVU in registrar.go re registry write errors
NOP  gofmt affected files
MOD update README & distinguish info logger
NOP
MOD change --verbose to --quiet. Again, verbose by default.
Require Go 1.3
Allow go 1.1 to 1.3
Revert "Allow go 1.1 to 1.3"

This reverts commit 361cb9354e237e347b6a094ba376a47e84b7a7e5.
FIX bug in harvester offset updates
Note:   fix by Christian Dahlqvist (https://github.com/cdahlqvist)
PR-Ref: https://github.com/elasticsearch/logstash-forwarder/pull/249/commits
Merge branch 'cleanup-ref-69142e7'

Reviewd by Jordan Sissel(@jordansissel)  & Jason Woods (@driskell).
Prevent closing the wrong connection

In the event of an SSL error (eg, bad certificate from a client), `client` here still pointed to the last successful connection.
So when a client failed to connect, and `client` still pointed to the last successful connection, we were forcing that good connection to be closed.

This PR sets `client` to `nil`, before accepting a new connection, and then tests to make sure it's not `nil`, before closing it.
Merge pull request #264 from avleen/patch-1

Prevent closing the wrong connection
Config file handling improvements:
 * Load multiple configuration files from a directory
 * Ignore empty configuration files
 * Filter '#' style comments from JSON configs