Merge lp:~mterry/duplicity/fix-drop-u1 into lp:duplicity/0.6
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 973 |
Proposed branch: | lp:~mterry/duplicity/fix-drop-u1 |
Merge into: | lp:duplicity/0.6 |
Diff against target: |
165 lines (+39/-50) 2 files modified
duplicity/backend.py (+39/-49) po/POTFILES.in (+0/-1) |
To merge this branch: | bzr merge lp:~mterry/duplicity/fix-drop-u1 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+216387@code.launchpad.net |
Description of the change
Looks like when the drop-u1 branch got merged, its conflict got resolved badly. Here is the right version of backend.py to use (and also drops u1backend.py from POTFILES).
To post a comment you must log in.
Kinda surprised the merge failed. I resolved the conflict by selecting
'resolve using other', which should have just taken your copy as is.
On Thu, Apr 17, 2014 at 3:00 PM, <email address hidden> wrote:
> The proposal to merge lp:~mterry/duplicity/fix-drop-u1 into lp:duplicity /code.launchpad .net/~mterry/ duplicity/ fix-drop- u1/+merge/ 216387 /code.launchpad .net/~mterry/ duplicity/ fix-drop- u1/+merge/ 216387 _______ _______ _______ _______ _______ _____ /launchpad. net/~duplicity- team /launchpad. net/~duplicity- team /help.launchpad .net/ListHelp
> has been updated.
>
> Status: Needs review => Merged
>
> For more details, see:
> https:/
> --
> https:/
> Your team duplicity-team is requested to review the proposed merge of
> lp:~mterry/duplicity/fix-drop-u1 into lp:duplicity.
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>