Document glob behavior with trailing slash

[René 'Necoro' Neumann]

With bug #1479545, globbing was changed (or restored) to behave differently, when the pattern has a trailing /. This fix silently broke my backup, as I had given
  --include /var/vmail/ --exclude '**', thus removing all emails from the backup.
This line had worked for quite some time...

While I understand the rationale behind the change in the aforementioned bug, it breaks the general assumption that /some/dir and /some/dir/ are equivalent (i.e. when no globbing is involved).

At the very least, it should be documented prominently! Currently it is not mentioned at all in the man-page...

[Andrew Coulton (acoulton)]

Hi,

This also bit me - I appreciate the new behaviour is probably correct, but this is a fairly major breaking change for anyone who had (intentionally or otherwise) been relying on a trailing / path matching the files within it. It's particularly tricky to notice with large sparsely populated directory structures, as the backup is still quite big with the directory skeleton so it's not immediately obvious there's actually nothing there.

I agree at the very least this ought to be flagged in the documentation in a major way (and should have been much more prominent in the changelog) but ideally duplicity would also print a warning to the console when a trailing / is present to give the user maximum chance to understand what that's doing.