aboutsummaryrefslogtreecommitdiff
path: root/system/duplicity
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 12:10:19 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:05 -0400
commit2b1e77bcad0763acbd64e33ec681249be93ae3b2 (patch)
tree68d404364dd3ce903d546c9cf789160e36732ee4 /system/duplicity
parent0616e3bdb65a3ec5c47c8b684742a8914b227308 (diff)
system/duplicity: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/duplicity')
-rw-r--r--system/duplicity/README13
1 files changed, 7 insertions, 6 deletions
diff --git a/system/duplicity/README b/system/duplicity/README
index 7f2d79d0643f..ee7d5ab755cb 100644
--- a/system/duplicity/README
+++ b/system/duplicity/README
@@ -1,8 +1,9 @@
duplicity - Encrypted bandwidth-efficient backup using rsync algorithm
-Duplicity backs up directories by producing encrypted tar-format volumes and
-uploading them to a remote or local file server. Because duplicity uses
-librsync, the incremental archives are space efficient and only record the
-parts of files that have changed since the last backup. Because duplicity
-uses GnuPG to encrypt and/or sign these archives, they will be safe from
-spying and/or modification by the server.
+Duplicity backs up directories by producing encrypted tar-format
+volumes and uploading them to a remote or local file server. Because
+duplicity uses librsync, the incremental archives are space efficient
+and only record the parts of files that have changed since the last
+backup. Because duplicity uses GnuPG to encrypt and/or sign these
+archives, they will be safe from spying and/or modification by the
+server.