comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 16 Nov 2015 18:15:53 +0000 (14:15 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 16 Nov 2015 18:15:53 +0000 (14:15 -0400)
doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c/comment_1_e4a67f2feaf7060ce56c37d6a82b5003._comment [new file with mode: 0644]

diff --git a/doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c/comment_1_e4a67f2feaf7060ce56c37d6a82b5003._comment b/doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c/comment_1_e4a67f2feaf7060ce56c37d6a82b5003._comment
new file mode 100644 (file)
index 0000000..b0158da
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-11-16T18:11:02Z"
+ content="""
+I think what's going on here is that -cfoo=bar is the same as -c foo=bar,
+and in this case the "foo" happens to contain a space. Since a -c config
+can be passed through to git to override any git config, git-annex doesn't
+try to validate them.
+"""]]