Merge lp:~mterry/duplicity/gio-name into lp:duplicity/0.6
Proposed by
Michael Terry
Status: | Merged |
---|---|
Approved by: | Kenneth Loafman |
Approved revision: | 724 |
Merged at revision: | 735 |
Proposed branch: | lp:~mterry/duplicity/gio-name |
Merge into: | lp:duplicity/0.6 |
Diff against target: |
45 lines (+6/-6) 1 file modified
duplicity/backends/giobackend.py (+6/-6) |
To merge this branch: | bzr merge lp:~mterry/duplicity/gio-name |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+63565@code.launchpad.net |
Description of the change
I've recently discovered that sometimes (at least on WebDAV), the server will not provide a GIO "display name", but will provide a GIO "name". (one is utf-8 formatted and is designed for user-presentation, the other is just a filename)
Since these strings aren't presented to user (just used in list results and get, put, and delete arguments), using just 'name' is fine.
And 'name' will always be available, whereas display name won't.
To post a comment you must log in.