duplicity-team team mailing list archive

[edso <edgar.soldin@xxxxxx>]

edso has proposed merging lp:~ed.so/duplicity/manpage.fixes into lp:duplicity.

Requested reviews:
  duplicity-team (duplicity-team)

For more details, see:
https://code.launchpad.net/~ed.so/duplicity/manpage.fixes/+merge/311405

fix html output via rman on the website
-- 
Your team duplicity-team is requested to review the proposed merge of lp:~ed.so/duplicity/manpage.fixes into lp:duplicity.

=== modified file 'bin/duplicity.1'
--- bin/duplicity.1	2016-11-01 19:26:03 +0000
+++ bin/duplicity.1	2016-11-21 15:20:29 +0000
@@ -1726,7 +1726,6 @@
 will distinguish between different backups.
 
 .SH A NOTE ON MULTI BACKEND
-
 The multi backend allows duplicity to combine the storage available in
 more than one backend store (e.g., you can store across a google drive
 account and a onedrive account to get effectively the combined storage
@@ -1736,58 +1735,46 @@
 Each element of the list must have a "url" element, and may also contain
 an optional "description" and an optional "env" list of environment
 variables used to configure that backend.
-
 .SS Query Parameters
-
 Query parameters come after the file URL in standard HTTP format
 for example:
-
+.RS
 .nf
-.RS
 multi:///path/to/config.json?mode=mirror&onfail=abort
 multi:///path/to/config.json?mode=stripe&onfail=continue
 multi:///path/to/config.json?onfail=abort&mode=stripe
 multi:///path/to/config.json?onfail=abort
+.fi
 .RE
-
 Order does not matter, however unrecognized parameters are considered
 an error.
-
 .TP
 .BI "mode=" stripe
-
 This mode (the default) performs round-robin access to the list of
 backends. In this mode, all backends must be reliable as a loss of one
 means a loss of one of the archive files.
-
 .TP
 .BI "mode=" mirror
-
 This mode accesses backends as a RAID1-store, storing every file in
 every backend and reading files from the first-successful backend.
 A loss of any backend should result in no failure. Note that backends
 added later will only get new files and may require a manual sync
 with one of the other operating ones.
-
 .TP
 .BI "onfail=" continue
-
 This setting (the default) continues all write operations in as
 best-effort. Any failure results in the next backend tried. Failure
 is reported only when all backends fail a given operation with the
 error result from the last failure.
-
 .TP
 .BI "onfail=" abort
-
 This setting considers any backend write failure as a terminating
 condition and reports the error.
 Data reading and listing operations are independent of this and
 will try with the next backend on failure.
-
 .SS JSON File Example
+.RS
 .nf
-.RS
 [
  {
   "description": "a comment about the backend"
@@ -1807,8 +1794,8 @@
   "url": "file:///path/to/dir"
  }
 ]
+.fi
 .RE
-.fi
 
 .SH A NOTE ON PAR2 WRAPPER BACKEND
 Par2 Wrapper Backend can be used in combination with all other backends to