TimeVault Could Save Reverse Diffs Rather Than Copy FIles
Bug #159205 reported by
Brian Pitts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TimeVault |
In Progress
|
Medium
|
Unassigned | ||
Bug Description
My apologies if I've misunderstood the code, but from snap.py it looks like each time a file changes TimeVault stores a copy of the entire file rather than just the parts that changed. This means that a small change in a large file will cause lots of data to be stored redundantly. It would be nice if TimeVault would only store reverse diffs like rdiff-backup (http://
Revision history for this message
| SourceContact (sourcecontact) wrote | #1 |
| Changed in timevault: | |
| importance: | Undecided → Medium |
| status: | New → In Progress |
To post a comment you must log in.
You have not misunderstood the code :). rdiff-backup is a very cool application. Thanks for bringing it to my attention - I have started to look at the code to see if I can incorporate some of the techniques into TimeVault.