From 380cb754058026c094a228a2c5c39df0c96d3388 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" Date: Thu, 12 Nov 2015 17:09:38 +0000 Subject: [PATCH] initial complaint --- ...ption_value_passed_within_arg_for__-c.mdwn | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c.mdwn diff --git a/doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c.mdwn b/doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c.mdwn new file mode 100644 index 0000000000..2bf5ec772a --- /dev/null +++ b/doc/bugs/does_not_complain__47__fail_if_by_mistake_option_value_passed_within_arg_for__-c.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. + +spotted that in my script I have "incorrectly" passed both -c and its value within the same single argument ('-c annex....'). But surprisingly annex neither treated it correctly, nor complained that something was incorrectly passed in. Shouldn't it fail if option is not '-c' but '-c smthelse' or correctly treat the value in such as case? + +### What version of git-annex are you using? On what operating system? + +5.20151104+gitge9cdce6-1~ndall+1 + +### Please provide any additional information below. + +[[!format sh """ +$> ls -ld svgtune-0.2.0/README.rst +-rw------- 1 yoh yoh 9 Nov 12 12:03 svgtune-0.2.0/README.rst + +$> git-annex add --debug '-c annex.largefiles=exclude=*.rst' svgtune-0.2.0/README.rst +add svgtune-0.2.0/README.rst ok +(recording state in git...) + +$> ls -ld svgtune-0.2.0/README.rst +lrwxrwxrwx 1 yoh yoh 189 Nov 12 12:03 svgtune-0.2.0/README.rst -> ../.git/annex/objects/32/vx/SHA256E-s9--246c960678ee9a80aa6d2eff2f1df1debd590cb73aa5fed6cb4b13b8018599f5.rst/SHA256E-s9--246c960678ee9a80aa6d2eff2f1df1debd590cb73aa5fed6cb4b13b8018599f5.rst +"""]] + +[[!meta author=yoh]] +