Report when duplicity is 'done' with restoring a file
Bug #388725 reported by
Michael Terry
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
It would be nice if duplicity reported when it has applied the last patch to a given file during restore.
My understanding of the current code is that it keeps patching a file as volumes come in. This would be a message printed when it had applied the last patch to a given file and that file was not mentioned in any future volume.
Does duplicity know that information?
Related branches
lp:~vila/bzr/388725-progress-bar-config-option
- John A Meinel: Approve
-
Diff: 192 lines (+51/-32)6 files modifiedbzrlib/config.py (+7/-4)
bzrlib/tests/blackbox/test_debug.py (+3/-4)
bzrlib/tests/blackbox/test_diff.py (+4/-4)
bzrlib/tests/blackbox/test_locale.py (+17/-11)
bzrlib/ui/text.py (+16/-9)
doc/en/release-notes/bzr-2.6.txt (+4/-0)
Revision history for this message
| Kenneth Loafman (kenneth-loafman) wrote | #1 |
| Changed in duplicity: | |
| importance: | Undecided → Wishlist |
| Changed in duplicity: | |
| status: | New → Won't Fix |
To post a comment you must log in.
This would require duplicity to do a lookahead into the new volumes, something it currently does not do.