added support for swift endpoint_type
fixed long line
Update README to document --pool-size parameter to wal_push

Editorialized by Daniel Farina <daniel@fdr.io>
Add Joshua Gross as a contributor
Remove extra typoed period
Merge pull request #66 from brosner/add-endpoint-type

added support for swift endpoint_type
Added Brian Rosner to the CONTRIBUTORS file
Corrected an inaccurate log message that resulted from a copy-paste.
Fixed the delete command with 'before' on Swift by using the portable API for getting a container from a key
Adhere to coding convention as enforced by tests
Using streaming uploads and download with Swift.

Previous it read entire files and HTTP responses into memory before uploading
or writing them to disk, respectively. Now we read/write in chunks.
Simplify and adjust logging setup

Notably, logging will be set up and sent to stderr regardless of
keyword arguments to configure (that flexibility was never used
anyway) and does not depend if root handlers have already been
registered or not.

Prompted after seeing some of the gratuitous difficulty in debugging
for some people due to lack of output, attempt to streamline and
simplify the logging setup procedure.

There may be a loss here to how well WAL-E composes with other
applications were it used as a library, but there are no such users
known to date nor have they complained, so adjust the trade-off in
favor of a higher chance of getting diagnostics for WAL-E users and
hackers.
Provide nicer logging on non-existant files in the Swift backend.

This now works the same as the S3 backend.
Fixes bug in calling "delete [--confirm] retain" with no base backups.
v0.7a2
Fixes KiB per second calculations that gave incorrectly high values

time.clock() uses processor time, excluding the time spent doing I/O,
but I/O is what we want to measure when timing uploads, etc. Due to
that the KiB/s values were quite a bit higher than the actual transfer
speeds.

Use time.time instead, which measure wall-clock time.
Fix spelling error
Fix vestigial help string from the multi-backend refactor

In the end, the decision was to not attempt to make the credential
situation for each storage backend to appear hold too much in common,
because in practice, they do not: Swift has a litany of tunables, and
AWS has the AWS_SECURITY_TOKEN stuff, and so on.
Minimize the amount of treatment of argv in 'cmd'

Remove some defaults and fallbacks about argv that were not used.
Because of the 'console_scripts' behavior of setuptools, 'cmd.main'
must be able to accept zero arguments and is going to read 'sys.argv'
anyway, which is also the default behavior of 'argparse'.

This breaks a use case of calling 'cmd.py' directly as a toplevel
entry point for the sake of testing, but no known parties do this.
Move pg_xlog test fixture to another file

Done in preparation to have it be shared with other integration
testing, and to communicate that it is a mechanism used by multiple
consumers (soon).