Upload paths differ between initial and inotify-upload

[ctavan]

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

Which one is the intended behavior?

[JeremyGrosser]

The intention was that all paths should be converted to absolute

[ctavan]

Cool, that's what I thought as well: #19

[JeremyGrosser]

Merged.