configremote: Support --json and --json-error-messages
Seems unlikely to be too useful, but who knows. Moved the checkSafeConfig call to happen after an action is started, so it will be captured by --json-error-messages Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project
This commit is contained in:
parent
a242eabc7a
commit
de84abb210
3 changed files with 22 additions and 21 deletions
|
@ -41,9 +41,6 @@ These commands have been updated to support --json:
|
|||
* git-annex-upgrade
|
||||
* git-annex-initremote
|
||||
* git-annex-enableremote
|
||||
|
||||
Provisional list of commands that don't support --json and maybe should:
|
||||
|
||||
* git-annex-configremote
|
||||
|
||||
These commands could support json, but I punted:
|
||||
|
@ -57,6 +54,8 @@ These commands could support json, but I punted:
|
|||
|
||||
These commands have been reviewed and should not support json:
|
||||
|
||||
(Discussion welcome of course if you disagree..)
|
||||
|
||||
* git-annex-contentlocation, git-annex-lookupkey, git-annex-calckey,
|
||||
(plumbing, output already machine parseable)
|
||||
* git-annex-setkey (plumbing)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue