summaryrefslogtreecommitdiff
path: root/bugs/multiple___34__exclude__34___in_configuration_fails.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'bugs/multiple___34__exclude__34___in_configuration_fails.mdwn')
-rw-r--r--bugs/multiple___34__exclude__34___in_configuration_fails.mdwn31
1 files changed, 0 insertions, 31 deletions
diff --git a/bugs/multiple___34__exclude__34___in_configuration_fails.mdwn b/bugs/multiple___34__exclude__34___in_configuration_fails.mdwn
deleted file mode 100644
index 6201a06..0000000
--- a/bugs/multiple___34__exclude__34___in_configuration_fails.mdwn
+++ /dev/null
@@ -1,31 +0,0 @@
-The documentation for "exclude" says that it could be used multiple times:
-
->--exclude=EXCLUDE
-> regular expression for pathnames to exclude from backup (can be used multiple times)
-
-It works when used multiple times on the command line. However, when using a configuration with:
-
- [config]
- exclude = /foo
- exclude = /bar
- exclude = /baz
-
-...only the last item "/baz" is actually excluded from the backup.
-
----
-
-The documentation doesn't actually say this anywhere (oops, sorry), so you couldn't know: the right way of doing that in the config file is to use one exclude line and separate values with commas (spaces optional).
-
- [config]
- exclude = /foo, /bar, /baz
-
-That should work.
-
-Using multiple exclude-lines in the config would be better, but Python's ConfigParser library doesn't really deal well with that.
-
-I'll mark this bug closed when the obnam manpage explains how to do this with config files.
-
---liw
-
-It's now in the manual page in bzr and fix will be included in the next
-release. [[done]] --liw