Merge lp:~ed.so/duplicity/manpage into lp:duplicity/0.6

Proposed by Kenneth Loafman
Status: Merged
Merged at revision: 895
Proposed branch: lp:~ed.so/duplicity/manpage
Merge into: lp:duplicity/0.6
Diff against target: 380 lines (+101/-132)
1 file modified
bin/duplicity.1 (+101/-132)
To merge this branch: bzr merge lp:~ed.so/duplicity/manpage
Reviewer Review Type Date Requested Status
duplicity-team Pending
Review via email: mp+133811@code.launchpad.net

Description of the change

more formatting fixes, clarifications in sections EXAMPLES, FILE SELECTION

To post a comment you must log in.
lp:~ed.so/duplicity/manpage updated
895. By Kenneth Loafman

* Merged in lp:~ed.so/duplicity/manpage
  - more formatting fixes, clarifications in sections EXAMPLES, FILE SELECTION

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'bin/duplicity.1'
2--- bin/duplicity.1 2012-10-17 14:04:27 +0000
3+++ bin/duplicity.1 2012-11-11 01:40:25 +0000
4@@ -68,50 +68,39 @@
5 .SH SYNOPSIS
6 .B duplicity [full|incremental]
7 .I [options]
8-.I source_directory target_url
9+source_directory target_url
10
11 .B duplicity verify
12-.I [options]
13-.I [--file-to-restore <relpath>]
14-.I source_url target_directory
15+.I [options] [--file-to-restore <relpath>]
16+source_url target_directory
17
18 .B duplicity collection-status
19 .I [options]
20-.I target_url
21+target_url
22
23 .B duplicity list-current-files
24-.I [options]
25-.I [--time time]
26-.I target_url
27+.I [options] [--time time]
28+target_url
29
30 .B duplicity [restore]
31-.I [options]
32-.I [--file-to-restore <relpath>]
33-.I [--time time]
34-.I source_url target_directory
35-
36-.B duplicity remove-older-than
37-.I time
38-.I [options]
39-.I [--force]
40-.I target_url
41-
42-.B duplicity remove-all-but-n-full
43-.I count
44-.I [options]
45-.I [--force]
46-.I target_url
47-
48-.B duplicity remove-all-inc-of-but-n-full
49-.I count
50-.I [options]
51-.I [--force]
52-.I target_url
53+.I [options] [--file-to-restore <relpath>] [--time time]
54+source_url target_directory
55+
56+.B duplicity remove-older-than <time>
57+.I [options] [--force]
58+target_url
59+
60+.B duplicity remove-all-but-n-full <count>
61+.I [options] [--force]
62+target_url
63+
64+.B duplicity remove-all-inc-of-but-n-full <count>
65+.I [options] [--force]
66+target_url
67
68 .B duplicity cleanup
69-.I [options]
70-.I [--force]
71-.I target_url
72+.I [options] [--force] [--extra-clean]
73+target_url
74
75 .SH DESCRIPTION
76 Duplicity incrementally backs up files and directory
77@@ -291,7 +280,7 @@
78 .TP
79 .BI --allow-source-mismatch
80 Do not abort on attempts to use the same archive dir or remote backend
81-to back up different directories. duplicity will tell you if you need
82+to back up different directories. duplicity will tell you if you need
83 this switch.
84
85 .TP
86@@ -632,12 +621,9 @@
87 .I orig
88 in the backup as if it were the path
89 .I new.
90-Can be passed multiple times. An example:
91-.PP
92-.RS
93+Can be passed multiple times. An example:
94+
95 duplicity restore --rename Documents/metal Music/metal sftp://uid@other.host/some_dir /home/me
96-.PP
97-.RE
98
99 .TP
100 .BI "--rsync-options " options
101@@ -646,12 +632,9 @@
102 list should be of the form "opt1=parm1 opt2=parm2" where the option string is
103 quoted and the only spaces allowed are between options. The option string
104 will be passed verbatim to rsync, after any internally generated option
105-designating the remote port to use. Here is a possibly useful example:
106-.PP
107-.RS
108+designating the remote port to use. Here is a possibly useful example:
109+
110 duplicity --rsync-options="--partial-dir=.rsync-partial" /home/me rsync://uid@other.host/some_dir
111-.PP
112-.RE
113
114 .TP
115 .BI "--s3-european-buckets"
116@@ -759,10 +742,9 @@
117 differs slightly hence the options should therefore be given in the long option format described in
118 .BR ssh_config(5) ,
119 like in this example:
120-.RS
121-.PP
122+
123 duplicity --ssh-options="-oProtocol=2 -oIdentityFile=/my/backup/id" /home/me scp://uid@other.host/some_dir
124-.TP
125+
126 .B NOTE:
127 .I ssh paramiko backend
128 currently supports only the
129@@ -1000,18 +982,29 @@
130 system. The file selection system comprises a number of file
131 selection conditions, which are set using one of the following command
132 line options:
133-.BR --exclude ,
134-.BR --exclude-device-files ,
135-.BR --exclude-filelist ,
136-.BR --exclude-filelist-stdin ,
137-.BR --exclude-globbing-filelist ,
138-.BR --exclude-regexp ,
139-.BR --include ,
140-.BR --include-filelist ,
141-.BR --include-filelist-stdin ,
142-.BR --include-globbing-filelist ,
143-and
144-.BR --include-regexp .
145+.RS
146+--exclude
147+.br
148+--exclude-device-files
149+.br
150+--exclude-filelist
151+.br
152+--exclude-filelist-stdin
153+.br
154+--exclude-globbing-filelist
155+.br
156+--exclude-regexp
157+.br
158+--include
159+.br
160+--include-filelist
161+.br
162+--include-filelist-stdin
163+.br
164+--include-globbing-filelist
165+.br
166+--include-regexp
167+.RE
168 Each file selection condition either matches or doesn't match a given
169 file. A given file is excluded by the file selection system exactly
170 when the first matching file selection condition specifies that the
171@@ -1048,15 +1041,15 @@
172 .BR include-globbing-filelist ,
173 and
174 .B exclude-globbing-filelist
175-options accept
176+options accept some
177 .IR "extended shell globbing patterns" .
178-These patterns can contain the special patterns
179+These patterns can contain
180 .BR * ,
181 .BR ** ,
182 .BR ? ,
183 and
184-.BR [...] .
185-As in a normal shell,
186+.B [...]
187+(character ranges). As in a normal shell,
188 .B *
189 can be expanded to any string of characters not containing "/",
190 .B ?
191@@ -1076,66 +1069,52 @@
192 before duplicity sees them.
193
194 The
195-.BI "--exclude " pattern
196-option matches a file iff:
197-
198-.TP
199-.B 1.
200+.B --exclude
201+pattern option matches a file if:
202+.IP 1.
203 .I pattern
204 can be expanded into the file's filename, or
205-
206-.TP
207-.B 2.
208+.IP 2.
209 the file is inside a directory matched by the option.
210 .PP
211-.RE
212-Conversely,
213-.BI "--include " pattern
214-matches a file iff:
215-
216-.TP
217-.B 1.
218+Conversely, the
219+.B "--include "
220+pattern matches a file if:
221+.IP 1.
222 .I pattern
223-can be expanded into the file's filename,
224-
225-.TP
226-.B 2.
227+can be expanded into the file's filename, or
228+.IP 2.
229 the file is inside a directory matched by the option, or
230-
231-.TP
232-.B 3.
233+.IP 3.
234 the file is a directory which contains a file matched by the option.
235 .PP
236-.RE
237 For example,
238-.PP
239-.RS
240+
241 .B --exclude
242 /usr/local
243-.PP
244-.RE
245-matches /usr/local, /usr/local/lib, and /usr/local/lib/netscape. It
246+
247+matches e.g. /usr/local, /usr/local/lib, and /usr/local/lib/netscape. It
248 is the same as --exclude /usr/local --exclude '/usr/local/**'.
249-.PP
250-.RS
251+
252+Or
253+.br
254 .B --include
255 /usr/local
256-.PP
257-.RE
258+
259 specifies that /usr, /usr/local, /usr/local/lib, and
260-/usr/local/lib/netscape (but not /usr/doc) all be backed up. Thus you
261+/usr/local/lib/netscape (but not /usr/doc) all be backed up. Thus you
262 don't have to worry about including parent directories to make sure
263-that included subdirectories have somewhere to go. Finally,
264-.PP
265-.RS
266+that included subdirectories have somewhere to go.
267+
268+Finally,
269+.br
270 .B --include
271 ignorecase:'/usr/[a-z0-9]foo/*/**.py'
272-.PP
273-.RE
274+
275 would match a file like /usR/5fOO/hello/there/world.py. If it did
276 match anything, it would also match /usr. If there is no existing
277 file that the given pattern can be expanded into, the option will not
278-match /usr.
279+match /usr alone.
280
281 The
282 .BR --include-filelist ,
283@@ -1151,9 +1130,7 @@
284 interpreted similarly to the way
285 .I extended shell patterns
286 are, with a few exceptions:
287-
288-.TP
289-.B 1.
290+.IP 1.
291 Globbing patterns like
292 .BR * ,
293 .BR ** ,
294@@ -1161,40 +1138,33 @@
295 and
296 .B [...]
297 are not expanded.
298-
299-.TP
300-.B 2.
301+.IP 2.
302 Include patterns do not match files in a directory that is included.
303 So /usr/local in an include file will not match /usr/local/doc.
304-
305-.TP
306-.B 3.
307+.IP 3.
308 Lines starting with "+ " are interpreted as include directives, even
309 if found in a filelist referenced by
310 .BR --exclude-filelist .
311 Similarly, lines starting with "- " exclude files even if they are
312 found within an include filelist.
313-
314-.RE
315+.PP
316 For example, if file "list.txt" contains the lines:
317
318 .RS
319 /usr/local
320-.RE
321-.RS
322+.br
323 - /usr/local/doc
324-.RE
325-.RS
326+.br
327 /usr/local/bin
328-.RE
329-.RS
330+.br
331 + /var
332-.RE
333-.RS
334+.br
335 - /var
336+.RE
337
338-.RE
339-then "--include-filelist list.txt" would include /usr, /usr/local, and
340+then
341+.B "--include-filelist list.txt"
342+would include /usr, /usr/local, and
343 /usr/local/bin. It would exclude /usr/local/doc,
344 /usr/local/doc/python, etc. It neither excludes nor includes
345 /usr/local/man, leaving the fate of this directory to the next
346@@ -1215,26 +1185,25 @@
347 allowed). For instance, if the file "globbing-list.txt" contains the
348 lines:
349
350-.RE
351 .RS
352 dir/foo
353-.RE
354-.RS
355+.br
356 + dir/bar
357-.RE
358-.RS
359+.br
360 - **
361+.RE
362
363-.RE
364-Then "--include-globbing-filelist globbing-list.txt" would be exactly
365-the same as specifying "--include dir/foo --include dir/bar --exclude **"
366+Then
367+.B "--include-globbing-filelist globbing-list.txt"
368+would be exactly the same as specifying
369+.B "--include dir/foo --include dir/bar --exclude **"
370 on the command line.
371
372 Finally, the
373 .B --include-regexp
374 and
375 .B --exclude-regexp
376-allow files to be included and excluded if their filenames match a
377+options allow files to be included and excluded if their filenames match a
378 python regular expression. Regular expression syntax is too
379 complicated to explain here, but is covered in Python's library
380 reference. Unlike the

Subscribers

People subscribed via source and target branches

to all changes: