summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://joey.kitenet.net/ <joey@web>2012-01-03 00:35:00 +0000
committerGravatar admin <admin@branchable.com>2012-01-03 00:35:00 +0000
commiteec59e73623ab232a180ef7ff5edc6c2255ca156 (patch)
treeba3abb9510adf7456da0abd1a3bfed3e701e89e0 /doc
parent3e678b114047906c96977bb26f70feeb1749c430 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment b/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment
new file mode 100644
index 000000000..62881bfc7
--- /dev/null
+++ b/doc/bugs/conq:_invalid_command_syntax/comment_1_f33b83025ce974e496f83f248275a66a._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joey.kitenet.net/"
+ nickname="joey"
+ subject="comment 1"
+ date="2012-01-03T00:34:59Z"
+ content="""
+AFAICs, you probably just have a \"conq\" program that is running in the background and emitted this error.
+
+The error message is not part of git-annex; it does not run any \"conq\" thing itself. Although you could try passing the --debug parameter to check the commands it does run to see if one of them somehow causes this conq thing.
+"""]]