Fix initial backup on startup that got broken with 96cd44bf4077e70186c8ef83662facbe4ef11a34
Add --backup-switch that is also described in the README
Update usage instructions in README
Merge pull request #17 from ctavan/fix-initial-backup

Fix initial backup
Add --exclude option to allow changing the hardcoded '-tmp' filter.

- Add dest= parameter for --exclude optparser option
- Respect exclude option in initial backup_files
- Update README
Merge pull request #14 from ctavan/add-exclude-option

Add exclude option
Add --without-index option to skip creation of -listdir.json files.
Make keyname separator configurable and default to ':'
Merge pull request #15 from ctavan/make-index-creation-configurable

Make index creation configurable
Merge pull request #16 from ctavan/make-keyname-separator-configurable

Make keyname separator configurable
Enforce uploading with full path in initial uploads.

When passing a relative path to tablesnap, then the initial backup_files
upload will not create the absolute paths of the files in the S3 bucket
whereas the inotify-triggered uploads will.

Say you are in `/home/foo` and `start tablesnap bucket bar/` then initial
files will be uploaded as `hostname:bar/file` whereas the
inotify-triggered files will be uploaded as `hostname:/home/foo/bar/file`

See #18.
Merge pull request #19 from ctavan/always-upload-files-by-absolute-path

Enforce uploading with full path in initial uploads.
Updated changelog
Migrate from optparse to argparse.
Update README
Also listen for IN_CLOSE_WRITE events, not only IN_MOVED_TO.
Make listen events configurable
Update README
Merge pull request #23 from ctavan/also-listen-for-close-write-events

Make inotify events configurable
Add --include parameter.