)]}'
{"devstack/plugin.sh":[{"author":{"_account_id":6116,"name":"li,chen","email":"shchenli@cn.ibm.com","username":"chen-li"},"change_message_id":"4bc20dea5e36de066fce68f8dacd246d231d09fd","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"    # pull the agent code from the current code zuul has a reference to"},{"line_number":19,"context_line":"    export DIB_REPOLOCATION_amphora_agent\u003d$OCTAVIA_DIR"},{"line_number":20,"context_line":"    export DIB_REPOREF_amphora_agent\u003d$(git -c \"$OCTAVIA_DIR\" log -1 --pretty\u003d\"format:%H\")"},{"line_number":21,"context_line":"    TOKEN\u003d$(openstack token issue | grep \u0027 id \u0027 | get_field 2)"},{"line_number":22,"context_line":"    die_if_not_set $LINENO TOKEN \"Keystone failed to get token.\""},{"line_number":23,"context_line":""}],"source_content_type":"text/x-sh","patch_set":1,"id":"9ad45d7e_57050678","line":20,"range":{"start_line":20,"start_character":44,"end_line":20,"end_character":45},"updated":"2016-08-10 06:37:31.000000000","message":"Is this really works as expected ?\nFrom the git doc, -c \u0026 -C are very different:\n\nhttps://www.kernel.org/pub/software/scm/git/docs/\n\n-C \u003cpath\u003e\n\n    Run as if git was started in \u003cpath\u003e instead of the current working directory. When multiple -C options are given, each subsequent non-absolute -C \u003cpath\u003e is interpreted relative to the preceding -C \u003cpath\u003e.\n\n    This option affects options that expect path name like --git-dir and --work-tree in that their interpretations of the path names would be made relative to the working directory caused by the -C option. For example the following invocations are equivalent:\n\n    git --git-dir\u003da.git --work-tree\u003db -C c status\n    git --git-dir\u003dc/a.git --work-tree\u003dc/b status\n\n-c \u003cname\u003e\u003d\u003cvalue\u003e\n\n    Pass a configuration parameter to the command. The value given will override values from configuration files. The \u003cname\u003e is expected in the same format as listed by git config (subkeys separated by dots).\n\n    Note that omitting the \u003d in git -c foo.bar ... is allowed and sets foo.bar to the boolean true value (just like [foo]bar would in a config file). Including the equals but with an empty value (like git -c foo.bar\u003d ...) sets foo.bar to the empty string.","commit_id":"30c20ca0c40cb87256286350c2a556aaf88861a3"}]}