New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
diff against existing files #963
Comments
|
note: still no progress on that one, although in the upcomming 1.1 release you will be able to diff between already backed-up archives. To sum it up.
and then from within the virtualenv where you have borg 1.1+ you can borg diff.... |
Is this issue completely abandoned? |
@mortee Issue is not closed. But OTOH other stuff has higher priority and there are limited developer resources. |
the diff command (#177) is great in finding out what changed between different archives. however, it would also be useful to diff against existing files. i know that you can use FUSE to mount an archive and use external tools to diff against that, but it seems to me there are optimizations that could be done with an internal diff command. for example, one could diff an individual file and avoid the overhead of doing the FUSE mount and looking down the directory tree...
There was a discussion on the mailing list recently that touched on this subject: https://mail.python.org/pipermail/borgbackup/2016q2/000202.html
The text was updated successfully, but these errors were encountered: